Remove the need for zarf to know what kind of Distro is deployed.

[bdw617]

Most of the things that zarf needs to know about the distro aren't actually needed to be held in config:

1. default storage class, (we just ask the kubecontext which the default storage class is)
2. did zarf create the cluster? we should be able to create an object in kube-context that says zarf-made-me to figure out whether or not we are in appliance mode or not.

This will actually remove a bunch of logic in zarf that will help increase the flexibility especially if a user wants to have a custom zarf init package with a kubernetes deployment that is not k3s.