Update go version to 1.20.4

[RamakrishnanArun]

What this PR does / why we need it:
This PR upgrades the Go version to 1.20.3 and go-restful to 3.10.2 which resolves a number of security vulnerabilities.

How does this change affect the cardinality of KSM: (increases, decreases or does not change cardinality) Does not change

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #2054

[k8s-ci-robot]

This issue is currently awaiting triage.

If kube-state-metrics contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

[RamakrishnanArun]

I've run the Twistlock tool against this and the report shows no vulnerabilities.

[mrueg]

I'm fine with the go 1.20.3 bump, I would like to see go-restful merged in kubernetes/kubernetes#115067 (in particular because of kubernetes/kubernetes#115067 (comment) ) before we include this here.

[liam-verta]

@RamakrishnanArun
Perhaps you could update the PR to remove (per the suggestions) to only update Go version?

It would be better to get this merged and a new release out.

[RamakrishnanArun]

@liam-verta Thanks for your input. I think I misunderstood @mrueg 's comment. I understood it as a required change but only merged after the linked change in kubernetes/kubernetes#115067 merged first.

So the reason for adding the change in both was that I got security vulnerabilities in both the go version and the version of go-restful that I am indirectly using with this project. That's why I wanted to add both updates.

Should I split them into 2 different PRs? One for the Go version and then one for the Go-Restful version?

[mrueg]

For go-restful, I would suggest to reach out on kubernetes/kubernetes#115067
I doubt this is actually exploitable here though.
We use https://go.dev/security/vuln/ govulncheck here, which checks the affected codepaths.
Most of the other scanners use a noisy approach of simply checking go.mod files, which is unreliable.

[RamakrishnanArun]

Thank you @liam-verta @mrueg for your review and inputs!

[mrueg]

One last request, since this change has become a single line now. Can you rebase everything into a single commit?

[RamakrishnanArun]

@mrueg done! Single commit now.

[mrueg]

/lgtm

Thanks!

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mrueg, RamakrishnanArun

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 [mrueg]

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

[RamakrishnanArun]

When do you think the next release would be done?

[liam-verta]

@mrueg
When do you think the next release would be done? This addresses reported CVE in dependencies so it would be good to cut a new image.