Conform more to command line standards

Is your feature request related to a problem? Please describe.
A nicely written standard around command lines is available.. Bandit should strive to conform to these standards where possible.

For more info, see: https://clig.dev/

TODOs:

• Display help text when passed no options, the -h flag, or the --help flag. #814
• Display a concise help text by default.
• Provide a support path for feedback and issues. A website or GitHub link in the top-level help text is common.
• In help text, link to the web version of the documentation.
• In help, Lead with examples.
• Display the most common flags and commands at the start of the help text.
• Use formatting in your help text.
• If the user did something wrong and you can guess what they meant, suggest it.
• Display output as formatted JSON if --json is passed.
• Disable color if your program is not in a terminal or the user requested it. The NO_COLOR environment variable is set, the TERM environment variable has the value dumb, the user passes the option --no-color. #813
• Use a pager (e.g. less) if you are outputting a lot of text.
• Make it effortless to submit bug reports.
• Use standard names for flags, if there is a standard.

Start at Bandit’s command-line entry point and inspect the existing help, output, and flag handling against the linked clig.dev guidance. Choose one unchecked TODO with a defined scope, then verify that the corresponding CLI behavior and help text meet that item.