The operator-sdk scaffolder seems to have changed a lot since we bootstrapped the project wrt e2e tests.

We should take a look and integrate the existing test suite, which, for instance, covers the metrics endpoint tests: https://github.com/kubernetes-sigs/kubebuilder/tree/v4.3.1/testdata/project-v4/test/e2e

One difference with our tests, for instance, is that they now leverage CLI / kubectl based commands to interact with the test cluster. It should simplify a couple of things, and also allows more interactions such as fetching pod logs or running "exec" commands & catching its output.