Interface for handling PVCs in the kube method

Currently, it seems Podman supports the creation of PVCs, through Podman volumes, so if a container in a pod mounts a PVC, Podman will mount a Podman volume onto that container.

Using kubePlay() on a YAML containing a PVC spec should therefore create a Podman volume in the background, but I've observed that kubeDown(), doesn't actually do anything to PVCs specified in a YAML that is passed to it. So if I have a YAML that defines a PVC and a POD, on deletion the POD will get taken down, but nothing will happen to the PVC, so if I try to apply that same YAML again after having deleted it, I get an error saying that a volume already exists, since the original volume never got deleted. This behaviour sort of makes sense, Podman does not want to accidentally delete volumes because the whole point is to persist data, and that requires the volumes to never be deleted I guess.

There is also the issue of letting users tell Harpoon when they want to recreate the volume, there is currently no way for users to do that at the moment.

This would be worth it to look into if we want to clarify/enhance the use of PVCs with the kube method.