Adapt Github Actions to make it work with monorepos

[fmvilas]

The release process that we have on AsyncAPI is meant to work with repositories containing a single application or package. Since we want to make this repo a monorepo, we need to adapt the release process too.

[Shurtu-gal]

@fmvilas can I work upon this?

[KhudaDad414]

@Shurtu-gal Actually I am working on it right now. 😄

[Shurtu-gal]

Sure, happy to help if needed. 🚀 @KhudaDad414

[KhudaDad414]

/progress 90

this PR is going to solve the current issue that we are facing with craco. the workflow has been tested here but I haven't had a successful because of the docker issue in the studio app, in theory it should work in the main repo. other packages publish fine.

[KhudaDad414]

/progress 40

since we are using docker to publish the studio as a docker image, figuring out how to do it in a monorepo since there is no package-lock.json in each app, so the docker publishing process needs to be reevaluated.

[fmvilas]

In case it helps, I found this: npm/rfcs#554.

[KhudaDad414]

/progress 95

changesets are going to replace the semantic-release processes. PR is ready for review. #706