[main] Upgrade to latest dependencies

[knative-automation]

Cron. -knative-sandbox

/cc @nlopezgi @zhongduo /assign @nlopezgi @zhongduo

Produced via:

./hack/update-deps.sh --upgrade --release v0.22
./hack/update-codegen.sh

Details:

bumping knative.dev/eventing fe6886b...418df62:
  > 418df62 Adjust resources.requests of eventing-webhook (# 5125)
bumping knative.dev/serving aeae909...b5d1348:
  > b5d1348 Add a benchmark for the entire handler chain of the activator (# 11014)
  > ccf35f1 Update net-istio nightly (# 11002)
  > 069c635 add to mon reviewers (# 10972)
  > 0e8410a Format markdown (# 11001)
  > 3e2b15e Collapse revision context into specialized context to avoid allocations (# 11009)
  > 4e5fde5 Only allocate named logger if necessary in activator (# 11008)
  > 9ee92b1 Default PeriodSeconds of the readiness probe to 1 if unset (# 10992)
  > 27757ec Fix concurrency reporter log to use the correct key (# 11007)
  > 60a7f99 Add lint for aliasing autoscaling import correctly (# 10885)
  > 05f16c6 Update net-kourier nightly (# 10989)
  > decdaf4 Update net-contour nightly (# 10988)
  > b7ef994 Add ux issue template to community contact instructions (# 10993)
  > 08e4e0e Update net-kourier nightly (# 10977)
  > 9cdf9b0 Update net-certmanager nightly (# 10976)
  > a78e43e Update net-istio nightly (# 10974)
bumping knative.dev/pkg dfeeb18...b558677:
  > b558677 Use TB interface, rather than T pointer when doing test stuff (# 2064)
  > 9bf9eeb rename downstream-test-go to actions-downstream-test (# 2065)

[knative-prow-robot]

Hi @knative-automation. Thanks for your PR.

I'm waiting for a google 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](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[zhongduo]

/ok-to-test /approve /lgtm

[knative-prow-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: zhongduo

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](https://github.com/google/knative-gcp/blob/main/OWNERS)~~ [zhongduo] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

[eclipselu]

Getting the following error in integration-tests/wi-tests, https://github.com/google/knative-gcp/pull/2185 and https://github.com/google/knative-gcp/pull/2187 are also affected.

Starting authentication check test for brokercell.
broker.eventing.knative.dev/warmup-broker created
Starting authentication check test which is running outside of the broker related Pods.
Waiting until brokercell authentication check pending.
ERROR: timeout waiting for brokercell authentication check pending with correct key message: authentication is not configured
Error from server (NotFound): brokercells.internal.events.cloud.google.com "default" not found
brokercell object YAML: 
ERROR: test setup failed

[tommyreddad]

@eclipselu This should be fixed once the next eventing nightly release goes out by tomorrow, following https://github.com/knative/eventing/pull/5134

[eclipselu]

@eclipselu This should be fixed once the next eventing nightly release goes out by tomorrow, following knative/eventing#5134

great, thanks for checking!

[tommyreddad]

/retest

[tommyreddad]

/lgtm

[tommyreddad]

/retest