[feature] Allow `hauler` to delete artifacts from the `store`

[zackbradys]

Is your feature request related to a problem? Please describe.

• Yes, operators are not able to delete anything once added to the store

Describe the solution you'd like

• Allow operators to delete/remove content and artifacts from the store

Possible Implementation:

• hauler store delete <reference name>

zackbradys@Zacks-MBP Downloads % hauler store -h
Interact with hauler's embedded content store

Usage:
  hauler store [flags]
  hauler store [command]

Aliases:
  store, s

Available Commands:
  add         Add content to store
  copy        Copy all store contents to another OCI registry
  delete      Delete content from the store
  extract     Extract content from the store to disk
  info        Print out information about the store
  load        Load a content store from a store archive
  save        Save a content store to a store archive
  serve       Expose the content of a local store through an OCI compliant registry or file server
  sync        Sync content to the embedded content store

Flags:
      --cache string   Location of where to store cache data (defaults to $XDG_CACHE_DIR/hauler)
  -h, --help           help for store
  -s, --store string   Location to create store at (default "store")

Global Flags:
  -l, --log-level string    (default "info")

Use "hauler store [command] --help" for more information about a command.

Describe alternatives you've considered

• Manually deleting the entire store with rm -rf <store name>

Additional context

• N/A

[dweomer]

initially described:

• Ensure content store's can be entirely declarative #58

[zackbradys]

adding this back on our radar... @amartin120

[HoustonDad]

Got a couple of customers requesting this