Support as many stactools subcommands as is reasonable

If we do want to be The One STAC CLI™, we should provide most of the functionality that exists in other CLis.

• add: Add an item to a catalog/collection.
• add-asset: Add an asset to an item or collection.
• add-raster: Add raster extension to an Item.
• copy: Copy a STAC Catalog
• create-item: Creates an item from an asset
• describe: Prints out a list of all catalogs, collections and items in this STAC.
• info: Display info about a static STAC catalog.
• layout: Reformat the layout of a STAC based on templating.
• [ ] lint: Lint a stac object with stac-check. Will not support, don't want to depend on stac-check
• merge: Merge items from one STAC into another.
• migrate: Migrate a STAC object to the latest version
• move-assets: Move or copy assets in a STAC catalog to the locations...
• summary: Summarize a STAC collection's contents.
• update-extent: Update a STAC collection's extent.
• update-geometry: Update an item geometry from an asset footprint
• validate: Validate a stac object.
• version: Display version info.

Start by reviewing the existing validate and version subcommands, then compare their structure with the unchecked command list. Determine which subcommand is the smallest viable addition and confirm its expected STAC behavior before implementing. Done means the selected command is supported and its behavior is covered by the project's existing checks.