feat: migrate to next

[Shurtu-gal]

Description:-

This is made to migrate the current react framework to NextJs 13

• Install Basic packages for next and initialise it
• Add tailwind support
• Setup web pack
• Setup services correctly to run on the server,
• Add support for MonacoEditor
• Add loader for YAML and JSON files.
• Clean up the packages
• Update the actions
• Write some basic tests.

Related issues:-

Resolves #684

[netlify]

✅ Deploy Preview for asyncapi-studio-design-system ready!

Name	Link
🔨 Latest commit	5bd6976
🔍 Latest deploy log	https://app.netlify.com/sites/asyncapi-studio-design-system/deploys/64af9f4a9984b50008662a98
😎 Deploy Preview	https://deploy-preview-701--asyncapi-studio-design-system.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[netlify]

❌ Deploy Preview for modest-rosalind-098b67 failed.

Name	Link
🔨 Latest commit	5bd6976
🔍 Latest deploy log	https://app.netlify.com/sites/modest-rosalind-098b67/deploys/64af9f4a7349c30008257dc1

[fmvilas]

Can you please edit the description of this PR and add "resolves #684"? This way GitHub would link this PR to the issue :)

[Shurtu-gal]

Done also added some tasks to do it methodologically. Do suggest if something is missing. 😃

[fmvilas]

That looks perfect mate 👍

[changeset-bot]

⚠️ No Changeset found

Latest commit: 5bd6976

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[Shurtu-gal]

@fmvilas I have added the hooks architecture. Do tell me if this will work.

[fmvilas]

It's amazing mate! You're doing a great effort 👏 What do you think it's best? I have the feeling that we can't merge this confidently and expect it to work the same as it's in production right now. Do you think it would be best to start development in a separate folder and slowly make sure it's going well?

[sonarcloud]

SonarCloud Quality Gate failed.   

1 Bug
0 Vulnerabilities
1 Security Hotspot
58 Code Smells

No Coverage information
0.0% Duplication

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