pin setup-envtest to fix test breakage

[kim-tsao]

Description

Current PR tests are failing due to this error:
go: sigs.k8s.io/controller-runtime/tools/setup-envtest@latest (in sigs.k8s.io/controller-runtime/tools/setup-envtest@v0.0.0-20240326031119-8afbb50e0eb2): go.mod:3: invalid go version '1.22.0': must match format 1.23

as a result of this change kubernetes-sigs/controller-runtime#2720 (comment)
We need to pin to an older commit in order to work around this.

Which issue(s) does this PR fix or relate to

• Fixes #issue_number

PR acceptance criteria

• Tests
• Documentation
• If the bundle manifests have been updated, make sure to review the rhdh-operator.csv.yaml file accordingly

How to test changes / Special notes to the reviewer

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

[github-actions]

PR images are available:

1. https://quay.io/janus-idp/operator:0.2.0-pr-278-5676193
2. https://quay.io/janus-idp/operator-bundle:0.2.0-pr-278-5676193
3. https://quay.io/janus-idp/operator-catalog:0.2.0-pr-278-5676193

[rm3l]

Thanks!

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rm3l

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [rm3l]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[rm3l]

/cherry-pick 1.1.x

Cherry-picking this in 1.1.x because PR tests on this branch are failing for the same reason.

[openshift-cherrypick-robot]

@rm3l: new pull request created: #280

In response to this:

/cherry-pick 1.1.x

Cherry-picking this in 1.1.x because PR tests on this branch are failing for the same reason.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.