Backport of Fix CVEs by updating controller-runtime into release/1.0.x

[hc-github-team-consul-core]

Backport

This PR is auto-generated from #2183 to be assessed for backporting due to the inclusion of the label backport/1.0.x.

🚨

Warning automatic cherry-pick of commits failed. If the first commit failed,
you will see a blank no-op commit below. If at least one commit succeeded, you
will see the cherry-picked commits up to, not including, the commit where
the merge conflict occurred.

The person who merged in the original PR is:
@t-eckert
This person should manually cherry-pick the original PR into a new backport PR,
and close this one when the manual backport PR is merged in.

merge conflict error: POST https://api.github.com/repos/hashicorp/consul-k8s/merges: 409 Merge conflict []

The below text is copied from the body of the original PR.

---

Fixes https://hashicorp.atlassian.net/browse/NET-704

Changes proposed in this PR:

• Bump version of controller runtime
• Update all breaking changes for this fix

How I've tested this PR:

• Built and run unit tests

How I expect reviewers to test this PR:

Checklist:

• Tests added
• CHANGELOG entry added

  HashiCorp engineers only, community PRs should not add a changelog entry.
  Entries should use present tense (e.g. Add support for...)

---

Overview of commits

• 9d49115 - 933b4fb - 91e2a1b - fbc460b - 23c30d3 - c310b2e - 3fe7b36 - 643ef89 - 9b374dd

[hashicorp-cla]

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes

---

temp seems not to be a GitHub user.
You need a GitHub account to be able to sign the CLA.
If you have already a GitHub account, please add the email address used for this commit to your account.

_{Have you signed the CLA already but the status is still pending? Recheck it.}

[t-eckert]

Closing because I did it manually. This got messed up because part of the fix came in through the api-gateways merge.