Enable CLI interactions with the catalog

[abangser]

It would be amazing if we could do a catalog add/delete/list from the CLI as well as from the UI. In particular I am thinking of the case where I want to create cluster and then immediately add a few baseline catalog tools.

Some pseudo code could be:

$ kubefirst k3d create
$ kubefirst k3d catalog list

  argo-events
  argo-rollouts
  datadog-agent
  goldilocks
  kratix
  kubernetes-dashboard
  kyverno
  opencost
  polaris
  testkube
  tracetest

  To install, use `kubefirst k3d catalog add <tool>`
  For more details, you can add -h to any command including with the specific catalog item listed.

$ kubefirst k3d catalog add kratix -h

  Usage:
    kubefirst k3d catalog add kratix
    
  Flags:
    -h, --help   help for kratix
    -d, --data   json data object to configure Kratix installation

$ kubefirst k3d catalog add kratix

$ kubefirst k3d catalog remove kratix

A lot of assumptions in there, but I think that there is a goal to allow more configuration of catalog tools during installation on the UI. And I was thinking a simple way to get around that would be to provide a json/yaml config file via the CLI rather than trying to manage an installation path.

[fharper]

Thanks for the suggestion @abangser. As mentioned on Slack, it's a really good idea, and the terminal aficionado in me would love that, but not sure it will be a priority for now.

We also welcome users' contributions though :D