[Request] Configure Cryostat itself for Agent self-monitoring

It would be nice to have an ability to configure a Cryostat CR for self-monitoring using the Cryostat Agent pointed back at itself. Currently the self-monitoring capability is limited to `localhost:0` JMX type, but this misses some more advanced features like capturing heap dumps. I'm imagining this could be simply a CR property like `enableSelfMonitoring` which essentially just causes the Operator to add the `cryostat.io/namespace` and `cryostat.io/name` Deployment labels to Cryostat's own Pod template, pointing at its own deployment Namespace and CR name.

Start by locating the Cryostat CR configuration and the Operator logic that builds Cryostat's Pod template. Check how Deployment labels are applied, then determine how a self-monitoring property should map the Cryostat namespace and CR name to the specified labels. Done means an enabled CR causes those labels to appear on Cryostat's own Pod template and supports self-monitoring beyond localhost:0.

Written by the indexing model from the issue text.