feat: introduce monorepo to Generator Repo

[ayushnau]

Changes Added.

1. Turborepo Added.
2. Converted the generator repo to app, inside the turborepo.
3. Added the required scripts of the turborepo to the root package.json file.

Related issue(s)

Resolves #1044

[aeworxet]

@asyncapi/bounty_team

[derberg]

Some stuff needs update because of docs related links and automation:

• doc hooks.md need update of links pointing to GH that would break, change them to relative link from website, which will be /docs/tools/generator/api
• workflow update-docs-in-website needs an update of link that now point to /generator/docs/, and probably should point to /generator/apps/generator/docs/

[derberg]

additionally:

• update PR title to match the reality - filters are not here in first iteration
• you have merge conflicts
• tests are failing, I suggest running them locally and integration tests fails with Error: An error occurred trying to start process '/usr/bin/bash' with working directory '/home/runner/work/generator/generator/./test/test-project'. No such file or directory which probably means some paths in tests also need an update
• also regular PR testing workflow fails on installation of dependencies, like npm ci is not working with turbo 🤔

[AyushNautiyalDeveloper]

Some stuff needs update because of docs related links and automation:

* doc hooks.md need update of links pointing to GH that would break, change them to relative link from website, which will be `/docs/tools/generator/api`

* workflow update-docs-in-website needs an update of link that now point to `/generator/docs/`, and probably should point to `/generator/apps/generator/docs/`

1. in first point you mean https://github.com/asyncapi/generator/blob/master/docs/api.md to https://github.com/asyncapi/generator/blob/master/apps/generator/docs/api.md

[derberg]

@AyushNautiyalDeveloper no, it just should be /docs/tools/generator/api as I wrote, a relative link, asyncapi.com relative - add it to asyncapi.com and you will see what I mean -> https://www.asyncapi.com/docs/tools/generator/api

links in docs do not have to work in github in markdown, they need to work in website, where people read them

[ayushnau]

@derberg

1. updated all the links.
2. The Integration tests are working now.
3. The npm ci is working fine.

[derberg]

• why we have apps/generator/.gitignore instead of having one gitignore in root?

• I believe apps/generator/assets/readme-banner.png must stay in the root

• apps/generator/.releaserc should also stay in root, right? it is a release config file and should be same for all, no?

• please add some Development guide to readme, that explains what I need to do locally to start the project, run tests

• please also explain how pushing to npm will work now. This is current release workflow https://github.com/asyncapi/generator/blob/master/.github/workflows/if-nodejs-release.yml where for example you can see we need npm test available in the root, that will trigger all tests of all projects

• also, the plan was filters are not in the PR but another one, so we should not have all these filters scripts in package.json

• did you run all tests on local? are you sure we do not need to make any amendments in test/test-project/test.sh ?

[derberg]

should we really point to latest? isn't it risky and error prone?

[ayushnau]

made it to the current latest version.

[derberg]

what we need it for? we do not use ts here anyway?

[ayushnau]

removed

[ayushnau]

@derberg

1. We need gitignore in the apps/generator for the test file that we dont want to be pushed. also adding those commands in root gitignore will not be applicable to all the apps. And also having multiple gitignore files for the turborepo is common pattern
2. updated the readmd file to correct place. Also I guess the readmd file for the generator should move to generator itself. so that we can add general
3. Added the required files to root.

Also i found that the test are not running properly with the current version. the issue is still not fixed
finding ways to run the tests.correctly. and currently i am working on this.

[derberg]

@ayushnau how is it going, do you need anything?

[sonarcloud]

Quality Gate failed

Failed conditions
4 Security Hotspots
9.3% Duplication on New Code (required ≤ 3%)
C Reliability Rating on New Code (required ≥ A)

See analysis details on SonarCloud

Catch issues before they fail your Quality Gate with our IDE extension SonarLint

[ayushnau]

This pr is moved to #1213