Value Statement

Ensure the issue title clearly reflects the value of this user story to the
intended persona. (Explain the "WHY")

Downstream builds for various ACM versions have been updated to use golang 1.21.

We should update our upstream to also use golang 1.21 so we don't get any surprises with compatibility.

• [x] Update cluster-backup-operator upstream to use golang 1.21
  • [x] release-2.7
  • [x] release-2.8
  • [x] release-2.9
  • [x] release-2.10
• [x] Update prow jobs (in openshift/operators) to use golang 1.21
• [x] Update volsync-addon-controller upstream to use golang 1.21
  • [x] release-2.7
  • [x] release-2.8
  • [x] release-2.9
  • [x] release-2.10
• [x] Update volsync operator (v0.9.z already ok, but v0.8.z needs update) to use golang 1.21

Definition of Done for Engineering Story Owner (Checklist)

• ...

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the [Customer
  Portal_doc_issue template](
  https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
  and ensure doc acceptance criteria is met. Link the development issue to
  the doc issue.
• [ ] Provide input to the QE team, and ensure QE acceptance criteria
  (established between story owner and QE focal) are met.

Support Readiness

• [ ] The must-gather script has been updated.