Get Superset + our Helm chart to work on MiniKube and document the process

[mistercrunch]

More context here -> #27434

As we decided to have docker-compose be more dedicatd to support development workflows exclusisvely, we're looking to provide a single-host solution.

This discussion is about testing the viability of minikube to be the dedicated production-ready setup for small scale/quickstart environments. If it is viable, we'll document and send folks int that direction.

[mistercrunch]

This PR adds pointers to minikube -> #27540

For the record, I pretty much just took 10 minutes to:

• brew install minikube
• cp helm/superset/values.yaml /tmp/superset-helm-values.yaml
• edited that file to put in a SECRET_KEY (won't work if you don't change it, as expected, for production no one should use the default secret, so that's good). The messages were pretty clear, but had to kubectl get pods, see error states and kubectl logs {pod_id} to see it
• helm upgrade --install --values /tmp/superset-helm-values.yaml superset superset/superset
• kubectl port-forward {pod_id} :8088
• everything seems to work as expected

I think that kind of settles it for me, seems super easy an totally viable. Now if you want to setup your own postgres on RDS or similar you have to start going a bit deeper, we could be more upfront about the need to set up your database as opposed to using the default postgres-in-docker/k8s set up.

Any reason why this isn't viable for anyone out there coming from docker-compose or other single-host-type setups?