Distinguish meta CLI commands like version and completion in docs site

[david-crespo]

Target component

• CLI
• SDK
• Something else
• Not sure

Overview

It would be nice to put information in the CLI docs JSON to allow the docs site to distinguish between commands like completion and version (possibly auth? meh, nah) and the rest, which have to do with actual API resources.

Implementation details

Two ideas:

• Give tags to top-level CLI commands to allow grouping in docs site sidebar, like we do with the API endpoints. In the API, endpoints with a tag starting with system/ get grouped under System and the rest go under Developer.
• Don't do formal grouping or tagging, but put completions and version under a top-level oxide self command so they at least take up less space and it's easier to tell they don't have anything to do with the API itself.

[karencfv]

Don't do formal grouping or tagging, but put completions and version under a top-level oxide self command so they at least take up less space and it's easier to tell they don't have anything to do with the API itself.

I'm a little hesitant to remove completion and version from the top level commands. These are (by convention?) generally top level commands or global flags in most CLIs (I'd like to say all but I haven't used all CLIs that exist), so it's not unreasonable to say that users will likely be expecting these commands to be top level commands or global flags.

[ahl]

I like them as top level commands... and I think there might be opportunities to separate them out both in the generated docs as well as in the help message. Good idea, @david-crespo.

[david-crespo]

Yeah, I'm persuaded that keeping them top level and doing grouping is better.