feat: support command-specific help and improve display quality

[Souvikns]

Description

• Creating support for root and command level help components.
• Using ink to create beautiful help components.

Related issue(s)

Fixes #22

[Souvikns]

All help messages

asyncapi --help

asyncapi validate --help

asyncapi context --help

[Souvikns]

@derberg pr is ready for review.

[derberg]

love it mate!

how about in such cases:

$ asyncapi validate
Unable to perform validation. Specify what AsyncAPI file should be validated.

These are your options to specify in the CLI what AsyncAPI file should be used:
- You can use --file flag to provide a path to the AsyncAPI file: asyncapi validate --file path/to/file/asyncapi.yml
- You can use --context flag to provide a name of the context that points to your AsyncAPI file: asyncapi validate 
--context mycontext
- In case you did not specify a context that you want to use, the CLI checks if there is a default context and uses 
it. To set default context run: asyncapi context use mycontext
- In case you did not provide any reference to AsyncAPI file and there is no default context, the CLI detects if in 
your current working directory you have files like asyncapi.json, asyncapi.yaml, asyncapi.yml. Just rename your file
 accordingly.

or will it followup as now you just focused on part related to help?

[Souvikns]

Not all terminals have similar support for colors, so in some terminals, it is not looking good and also have visibility issue. Like in CMD -

[derberg]

@Souvikns I think it is ok if it is not that good in windows commander, I checked in basic mac terminal and it looks good. Imho it is acceptable

[derberg]

@Souvikns I approved but there is one more comment?

[derberg]

@Souvikns what about this comment + I see you removed the entire info about the version, but the version works fine, just problem is that only -v alias doesn't work out of the box, so please document just version

[Souvikns]

Then let me update it in the readme and as well as in the cli messages.

[Souvikns]

@derberg actually the way I have written the code it splits the flag alias and flag param for highlighting so it is coming something like this, does this look ok?

[derberg]

@Souvikns it would make sense to highlight --help too, so always highlight all flags imho

[Souvikns]

ok sure then.

[Souvikns]

The initial help message has been changed how shall we update the readme file to support this. Should I put a screenshot or just make some kind of walkthrough in the usage to how to access help messages for different commands.

[derberg]

make it easy now, we can beautify readme later, just screen shots of output from each help, or copy-paste of help text

[Souvikns]

Then should I update the readme in this PR?
I was thinking It would be good to have proper documentation of all the commands and have examples alongside it.

[derberg]

Yeah, just simple mupdate is needed of what we have now to reflect reality. Better docs, descriptions and some walkthrough can be done in a followup

[Souvikns]

@derberg does this look good. I guess adding an image for the root help we would have to update the image every time we add new commands.

[derberg]

@Souvikns I definitely agree that at this stage doing images would be to much. We should just update CLI section though, what you see after asyncapi --help and what after asyncapi context --help and asyncapi validate --help

[asyncapi-bot]

🎉 This PR is included in version 0.4.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀