Upgrade Argo Rollouts operator operator-sdk and controller-runtime version to match sibling gitops/argocd-operators

[jgwest]

The sibling operators to this project (argocd-operator and gitops-operator) have both upgraded to newer versions of operator-sdk, controller-runtime, and controller-gen. We should likewise upgrade to the same versions, to keep pace.

These are example PRs where the work was completed in sibling repositories, to give an idea of the work required.

argocd-operator:

• https://github.com/argoproj-labs/argocd-operator/pull/1447
• https://github.com/argoproj-labs/argocd-operator/pull/1449

gitops-operator:

• https://github.com/redhat-developer/gitops-operator/pull/742

Completion Criteria:

• Migrate to kubebuilder to go/v4 (see https://github.com/argoproj-labs/argocd-operator/pull/1449/files for example of kubebuilder change)
  • This appears to be mean moving main.go to cmd/main.go
  • Also moving controllers to internal/controller
  • Updating PROJECT file
  • Anything else we need to do?
• Migrate to newer operator-sdk version, controller-gen versions in Makefile
• Unit/E2E tests are passing, after changes

[jgwest]

Corresponding Red Hat JIRA tracker: https://issues.redhat.com/browse/GITOPS-5098