chore: bump trivy to v0.57.1 and use golang:1.22 in dockerfile

[aramase]

/kind failing-test

• The image scan CI job is flaking because of rate limit errors. Updating to the latest version of trivy to consume Mitigate rate limit issues by utilizing mirror.gcr.io as default DB repository aquasecurity/trivy#7938.
• Bumping the go base image to 1.22 to resolve CVEs.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aramase

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

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

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 36.54%. Comparing base (87f51ec) to head (041d142).
Report is 78 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1693      +/-   ##
==========================================
+ Coverage   35.83%   36.54%   +0.71%     
==========================================
  Files          63       63              
  Lines        3759     4526     +767     
==========================================
+ Hits         1347     1654     +307     
- Misses       2268     2729     +461     
+ Partials      144      143       -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[sozercan]

@aramase you might need to add mirrors to address this, see: https://github.com/open-policy-agent/gatekeeper/pull/3696/files

[aramase]

@aramase you might need to add mirrors to address this, see: https://github.com/open-policy-agent/gatekeeper/pull/3696/files

@sozercan I bumped it to v0.57.1 that has mirror.gcr.io (xref: aquasecurity/trivy#7668 (comment)).

[aramase]

/assign @enj

[aramase]

/cherry-pick release-1.4

[k8s-infra-cherrypick-robot]

@aramase: once the present PR merges, I will cherry-pick it on top of release-1.4 in a new PR and assign it to you.

In response to this:

/cherry-pick release-1.4

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.

[enj]

/lgtm

[k8s-infra-cherrypick-robot]

@aramase: new pull request created: #1702

In response to this:

/cherry-pick release-1.4

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.