fix: remove an error at the end of the -h "help" flag

[neoandmatrix]

Related issue(s)
Resolves #1625

Description
This PR helps to fix the ERROR message issue in the -h help command flag.

Approach

Upon going through the codebase i first tried to log more of error message and got the following for stack trace of the error message.

With referring to above trace and going through the oclif codebase i found that the error being shown here is not an actual error but just used to terminate the help command.
This is that particular code.

Then after carefully going through help command implementation in the oclif codebase and also referring to an already mentioned old issue about this bug and their solution i concluded that this error is safe to ignore as this is expected in the command output and is not critical.

@AayushSaini101 Please review this PR.
Thanks.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 937c501

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.

[asyncapi-bot]

Hello, @changeset-bot[bot]! 👋🏼

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

    At the moment the following comments are supported in pull requests:

    - `/please-take-a-look` or `/ptal` - This comment will add a comment to the PR asking for attention from the reviewrs who have not reviewed the PR yet.
    - `/ready-to-merge` or `/rtm` - This comment will trigger automerge of PR in case all required checks are green, approvals in place and do-not-merge label is not added
    - `/do-not-merge` or `/dnm` - This comment will block automerging even if all conditions are met and ready-to-merge label is added
    - `/autoupdate` or `/au` - This comment will add `autoupdate` label to the PR and keeps your PR up-to-date to the target branch's future changes. Unless there is a merge conflict or it is a draft PR. (Currently only works for upstream branches.)
    - `/update` or `/u` - This comment will update the PR with the latest changes from the target branch. Unless there is a merge conflict or it is a draft PR. NOTE: this only updates the PR once, so if you need to update again, you need to call the command again.

[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

[AayushSaini101]

Thank you for the PR : ) @neoandmatrix can you try to verify the changes via running in your local, to verify the changes and running local instructions are given in the contributions guideline of the CLI project

[neoandmatrix]

Thank you for the PR : ) @neoandmatrix can you try to verify the changes via running in your local, to verify the changes and running local instructions are given in the contributions guideline of the CLI project

Sure will verify and attach the screenshot of changes.

[neoandmatrix]

After doing the mentioned changes in PR and upon running the commands new file -h and start studio -h below are the before and after screenshots

Before changes :-
new file -h

start studio -h

After changes :-

new file -h

start studio -h

@AayushSaini101 Please verify.
Thanks.

[AayushSaini101]

/rtm