rapid reset remediation

[everettraven]

Description of the change:
Updates dependencies, implementations, testdata, and tests for the default operator-sdk scaffolds and base images for remediation of

• GHSA-qppj-fm5r-hxr3
• GHSA-4374-p667-p6c8

Some notable changes:

• Removal of the go/v3 testdata. This plugin version is deprecated. To keep the testdata and test logic straightforward and easier to maintain, limit the go operator testdata to use go/v4.
• Updating of the deprecated packagemanifests integration tests to use the go/v4 testdata, which required changing the install modes for OLM v0 to only supporting and installing as AllNamespaces mode due to mutating webhooks being present in the testdata.
• Bumps k8s dependencies to v0.28.5
• Bumps Kubebuilder to a commit where the default go/v4 scaffolding includes flags for disabling HTTP/2 on metrics and webhook servers and securely serving the metrics endpoint
• Bumps controller-runtime to v0.16.3 and includes associated changes.
• Adds flags to the helm operator controller for disabling HTTP/2 on metrics and webhook server and securely serving the metrics endpoint

Motivation for the change:

• Reduce the manual effort involved after scaffolding a new operator project to resolve:
  • GHSA-qppj-fm5r-hxr3
  • GHSA-4374-p667-p6c8

Checklist

If the pull request includes user-facing changes, extra documentation is required:

• Add a new changelog fragment in changelog/fragments (see changelog/fragments/00-template.yaml)
• Add or update relevant sections of the docs website in website/content/en/docs

[everettraven]

As mentioned in slack the replace section of the go.mod file can be replaces since all dependency versions there are now past the pinned versions. In my testing in of removing them for1.28 update there were no issues in go vet.

@acornett21 this should be done in b93b680

[everettraven]

ot sure if this is planned in another PR, but I think alot of documentation needs to change. I think anything that mentions option.Namespace and anything that talks about cache.MultiNamespacedCacheBuilder. There could be other things, but those are the main ones I see.

I don't think there is currently any PRs planned to update the docs, but I think it would be good to capture any necessary docs update in a new issue to prevent the size of this PR from blowing up any further. Would you mind capturing the problems you've seen as new issues?

[rashmigottipati]

Changes look good to me
/lgtm