Merge the studio-next and studio apps

[Shurtu-gal]

The studio-next folder was created for migrating to next.js. As the migration is complete now, it is time to remove the studio folder to decrease the redundancy.

Steps:

• Remove the studio folder.
• Check if there are any regressive problems or differences in the studio-next app as compared to the currently deployed site.
• @fmvilas I suppose we will have to edit the domain tracking at netlify as well.

[Shurtu-gal]

/gfi

[Shurtu-gal]

/help

[asyncapi-bot]

Hey @Shurtu-gal, your message doesn't follow the requirements, you can try /help.

[asyncapi-bot]

Hello, @Shurtu-gal! 👋🏼

I'm 🧞🧞🧞 Genie 🧞🧞🧞 from the magic lamp. Looks like somebody needs a hand!

At the moment the following comments are supported in issues:

• /good-first-issue {js | ts | java | go | docs | design | ci-cd} or /gfi {js | ts | java | go | docs | design | ci-cd} - label an issue as a good first issue.
  example: /gfi js or /good-first-issue ci-cd

[Shurtu-gal]

Tagging for visibility @Amzani @fmvilas.

[aeworxet]

Please do this task only after #1094 is merged.

Besides, special attention must be paid to paths, naming, and versioning:
https://github.com/asyncapi/studio/blob/master/apps/studio/package.json#L2
https://github.com/asyncapi/studio/blob/master/apps/studio-next/package.json#L2

[Shurtu-gal]

Please do this task only after #1094 is merged.

Sure. Just wanted to initiate it before we move along.

[aeworxet]

The migrated version also might get immediately broken due to #1094 (comment).

[aeworxet]

#1094 was merged, so pay attention to this change: #1094 (comment).

[aeworxet]

FYI
Hard-locked the @asyncapi/converter on version 1.5.0 during handling incident #1138.

[aeworxet]

#1120 was merged just now.

[prashantrai-30]

Hey @Shurtu-gal,can you assign this to me.

[Shurtu-gal]

Hey @prashantrai-30 already a PR has resolved this. I forgot to close this.