[Request] Kubernetes pod as target

### Describe the feature

We use Cryostat with Kubernetes target discovery and find that when a pod belonging to a StatefulSet is rescheduled, 1) the jvmId changes and 2) the Kubernetes discovery has 'modified the target' such that prior recordings are no longer accessible through the UI and indeed are not that easy to find in the S3 bucket directly.

It would greatly enhance usability for us if the pod name (and namespace) could be used as the identity for the target, as we always want to investigate what happened in such-and-such a pod at a particular time.

### Anything other information?

_No response_

Maintainer edit:
- #41
- #66
- #71

The issue names Kubernetes target discovery and the pod's namespace/name as the desired identity; begin by tracing how discovery assigns target identity and how recordings are associated with it. Done means a rescheduled StatefulSet pod retains access to prior recordings through the UI without relying on the changed jvmId.

Written by the indexing model from the issue text.