feat: added interactive steps to using asyncapi start studio command

[pseudo-tensor]

Fixes #1727
Added Interactive steps for asyncapi start studio command for specifying

• To start with a reference file
• Path or reference file
• Port value

[changeset-bot]

⚠️ No Changeset found

Latest commit: e9a008f

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.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

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

[github-actions]

Welcome to AsyncAPI. Thanks a lot for creating your first pull request. Please check out our contributors guide useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

[AayushSaini101]

/u

[AayushSaini101]

@pseudo-tensor thanks for the PR, kindly add screenshots for following case

• When the particular asyncapi document has been passed then show the result of UI
• What is the result no document passed in the command line, kindly add the result in this case thanks : )

[pseudo-tensor]

This is the result when we pass a specific file

When no reference is specified it falls back to its original behaviour and looks for the file asyncapi.yml

[pseudo-tensor]

@AayushSaini101 I've made changes to follow the eslint config provided.
Please suggest any further necessary changes

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[pseudo-tensor]

@AayushSaini101 should i add a .changeset in this PR?