[release-1.16] Upgrade to latest dependencies [skip-dot-release]

[knative-automation]

update knative.dev/hack to use latest GKE version -dsimansk

/cc knative-extensions/serving-writers
/assign knative-extensions/serving-writers

Produced by: knative-extensions/knobots/actions/update-deps

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 75.14%. Comparing base (74a76b5) to head (a444b2b).
Report is 1 commits behind head on release-1.16.

Additional details and impacted files

@@               Coverage Diff                @@
##           release-1.16     #825      +/-   ##
================================================
- Coverage         79.89%   75.14%   -4.76%     
================================================
  Files                17       17              
  Lines              1597     1597              
================================================
- Hits               1276     1200      -76     
- Misses              285      363      +78     
+ Partials             36       34       -2     

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[skonto]

@dsimansk could you bump the K8s version here too or we should override?

[dprotaso]

/lgtm
/approve

[knative-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dprotaso, knative-automation

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

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

[dprotaso]

/override "codecov/project"

[knative-prow]

@dprotaso: Overrode contexts on behalf of dprotaso: codecov/project

In response to this:

/override "codecov/project"

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.