[components] Move global options to subcommands

[smackesey]

Summary & Motivation

This changes the options scheme in dagster-dg so that options are no longer hierarchically processed and passed down the command tree. Instead, all leaves of the tree have the same set of "global options" appended to their options list. These are visually separated in the help message. We correspondingly simplify the Usage message to have a single [OPTIONS] input spot.

Before:

$ dg generate component --help

Usage: dg [OPTIONS] generate component [OPTIONS] COMPONENT_TYPE COMPONENT_NAME [EXTRA_ARGS]...

  Generate a scaffold of a Dagster component.

  ... description ...

Options:
  --json-params TEXT  JSON string of component parameters.
  -h, --help          Show this message and exit.

Options (dg):
  --builtin-component-lib TEXT  Specify a builitin component library to use.
  --verbose                     Enable verbose output for debugging.
  --disable-cache               Disable caching of component registry data.
  --clear-cache                 Clear the cache before running the command.
  --cache-dir PATH              Specify a directory to use for the cache.

How I Tested These Changes

Modified unit tests, played with it on the command line.

[smackesey]

• [components] Move global options to subcommands #26640 👈 (View in Graphite)
• [components] Change CLI from verb-noun to noun-verb #26623
• [components] Make dg generate code-location --use-editable-dagster include all dagster libs #26612
• [components] Move dagster-components test component lib to dagster_components.lib.test #26611
• [components] Add --rebuild-component-registry option, --skip-venv option, build cache on code loc construction #26591
• [components] Expose generation CLI params in dagster-dg #26478
• [components] Make dagster-dg help messages include parent options #26590
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.