[Request] Reports sidecars should be secured

### Describe the feature

When the Cryostat CR contains configuration to deploy Reports sidecars, the Operator should also place an auth proxy instance in front of these Pods. The Operator can generate a basic auth secret for this auth proxy to exclusively use, and can reconfigure the Cryostat container's reports service URL to include the basic auth credentials. This way the reports sidecar is not accessible by other processes within the cluster that can see its Service, but only by the Cryostat instance associated with the same CR.

### Anything other information?

_No response_

Start by tracing how the Operator deploys Reports sidecar Pods and configures the Cryostat reports service URL. Then inspect any existing auth proxy and generated basic-auth secret handling in the project. Done means Reports sidecars are protected by an auth proxy, credentials are scoped to the associated Cryostat instance, and the Cryostat container uses the protected URL.

Written by the indexing model from the issue text.