chore: upgrade to go 1.23.2

[andrewjamesbrown]

Fixes #N/A

Description
Pick up latest minor 1.23 release to address security vulnerabilities
https://go.dev/doc/devel/release#go1.23.minor

Specifically it addresses these:

% grype public.ecr.aws/karpenter/controller:1.0.6@sha256:25ec56d5bc718b213a648c0c64360a3be7fbe885b79905c73b77f68295352e9b
 ✔ Vulnerability DB                [no update available]
 ✔ Parsed image                                                                                     sha256:8a609f695a1dd5db4c85aab9e85fe97ac55b062f639643404c9cd67f04c6592a
 ✔ Cataloged contents                                                                                      ce005ceecbcc8627c0ecc91d767ea177b38db057a34fcbe2bc520e2881278308
   ├── ✔ Packages                        [99 packages]
   ├── ✔ File digests                    [1,128 files]
   ├── ✔ File metadata                   [1,128 locations]
   └── ✔ Executables                     [1 executables]
 ✔ Scanned for vulnerabilities     [3 vulnerability matches]
   ├── by severity: 0 critical, 2 high, 0 medium, 0 low, 0 negligible (1 unknown)
   └── by status:   3 fixed, 0 not-fixed, 0 ignored
NAME    INSTALLED  FIXED-IN        TYPE       VULNERABILITY   SEVERITY
stdlib  go1.22.5   1.22.7, 1.23.1  go-module  CVE-2024-34158  High
stdlib  go1.22.5   1.22.7, 1.23.1  go-module  CVE-2024-34156  High
stdlib  go1.22.5   1.22.7, 1.23.1  go-module  CVE-2024-34155  Unknown

How was this change tested?

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[k8s-ci-robot]

Welcome @andrewjamesbrown!

It looks like this is your first PR to kubernetes-sigs/karpenter 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/karpenter has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @andrewjamesbrown. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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-sigs/prow repository.

[coveralls]

Pull Request Test Coverage Report for Build 11578424808

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 9 unchanged lines in 2 files lost coverage.
• Overall coverage decreased (-0.03%) to 80.844%

---

Files with Coverage Reduction	New Missed Lines	%
pkg/controllers/provisioning/scheduling/nodeclaim.go	2	89.13%
pkg/controllers/provisioning/scheduling/preferences.go	7	86.67%

Totals
Change from base Build 11567200194:	-0.03%
Covered Lines:	8483
Relevant Lines:	10493

---

💛 - Coveralls

[jonathan-innis]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andrewjamesbrown, jonathan-innis

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 [jonathan-innis]

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