[Story] Scorecard test for built-in discovery

We should revisit adding a Scorecard test similar to `cryostat-recording` that uses built-in Kubernetes discovery instead of a custom target. We encountered some strange networking failures on the Cryostat end when trying this previously: https://github.com/cryostatio/cryostat-operator/pull/698#issuecomment-1885829894. Nevertheless, this is an important test to have so we should try to find some way to make it work, at least for 3.0+.

Start by reviewing the existing `cryostat-recording` Scorecard test and the networking failures discussed in pull request 698's linked comment. Compare that test with the requested built-in Kubernetes discovery path and verify the result against the Scorecard test setup. Done means a reliable test works for the intended 3.0+ versions without the previously encountered Cryostat-side networking failures.

Written by the indexing model from the issue text.