chore: Binaries incmd folder, examples in examples folder

[orpheuslummis]

RELEVANT ISSUE(S)

Resolves #500

DESCRIPTION

As described in the issue:

Use /cmd/ as the place for all our binaries, defradb, cmd docs generator, man pages generator (upcoming), etc. CLI remains as a package under /cli/. This is scalable and idiomatic to Go. Additionally introduces convenience for the cmd docs generator.

HOW HAS THIS BEEN TESTED?

Manual testing.

CHECKLIST:

• I have commented the code, particularly in hard-to-understand areas.
• I have made corresponding changes to the repo-held documentation.
• I have made sure that the PR title adheres to the conventional commit style (subset of the ones we use can be found under: tools/configs/chglog/config.yml

ENVIRONMENT / OS THIS WAS TESTED ON?

Please specify which of the following was this tested on (remove or add your own):

• Arch Linux
• Debian Linux
• MacOS
• Windows

[jsimnz]

Need to change all the files under cli/ that have the package name cmd to cli

[shahzadlone]

LGTM! made a minor non-blocking follow up comment.

[jsimnz]

LGTM.

Thought: Not a blocker on this PR, but was wondering if there is a benefit if we included a subcommand on the main defra binary called tools which may include docsgen, mangen, and future cli-completions stuff.

Can be done in a diff PR down the line tho.

[orpheuslummis]

Thought: Not a blocker on this PR, but was wondering if there is a benefit if we included a subcommand on the main defra binary called tools which may include docsgen, mangen, and future cli-completions stuff.

My first impression is that I'm in favor of it. It would allow to provide infrequently used tools in a CLI sub-namespace. As I understand it would require a different pattern than what is introduced in this PR. Taking note of it as a potential idea for CLI structure. Thanks.