Upgrade to latest dependencies

[creydr]

The automated dependency bump in #7182 has issues with a failing unit test.
This is because gomodules.xyz/jsonpatch/v2 did some internal performance changes in gomodules/jsonpatch#36. This leads not to a replace patch instead of an add and remove.
This PR addresses it and updates the failing unit test to take this into account.

[codecov]

Codecov Report

Patch coverage has no change and project coverage change: -0.02% ⚠️

Comparison is base (29ac3ee) 77.93% compared to head (8a3379c) 77.92%.
Report is 5 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #7190      +/-   ##
==========================================
- Coverage   77.93%   77.92%   -0.02%     
==========================================
  Files         246      246              
  Lines       13200    13202       +2     
==========================================
  Hits        10288    10288              
- Misses       2390     2392       +2     
  Partials      522      522              

see 1 file with indirect coverage changes

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

[creydr]

/hold
seems to be flaky

[creydr]

TestAllCases in pkg/reconciler/inmemorychannel is flaky for the case when adding a new subscriber and removing an existing and changing the order:

eventing/pkg/reconciler/inmemorychannel/dispatcher/inmemorychannel_test.go

Lines 194 to 211 in 19ab7b7

	Name: "with subscribers, one removed one added to status",
	Key: imcKey,
	Objects: []runtime.Object{
	NewInMemoryChannel(imcName, testNS,
	WithInitInMemoryChannelConditions,
	WithInMemoryChannelDeploymentReady(),
	WithInMemoryChannelServiceReady(),
	WithInMemoryChannelEndpointsReady(),
	WithInMemoryChannelChannelServiceReady(),
	WithInMemoryChannelSubscribers(subscribers),
	WithInMemoryChannelReadySubscriberAndGeneration(string(subscriber3UID), subscriber3Generation),
	WithInMemoryChannelReadySubscriberAndGeneration(string(subscriber1UID), subscriber1Generation),
	WithInMemoryChannelAddress(channelServiceAddress)),
	},
	WantPatches: []clientgotesting.PatchActionImpl{
	makePatch(testNS, imcName, oneSubscriberRemovedOneAddedPatch),
	},
	}, {

failed run: https://prow.knative.dev/view/gs/knative-prow/pr-logs/pull/knative_eventing/7190/unit-tests_eventing_main/1692134117669343232
succeeded run: https://prow.knative.dev/view/gs/knative-prow/pr-logs/pull/knative_eventing/7190/unit-tests_eventing_main/1692136356471377920

In 8a3379c I changed the test to replace a subscriber (instead of adding and removing one and changing the order), because that way the produced patch is more predictable (and thus not flaky). It is not exactly testing, what was tested before, but IMO it's testing to replace a subscriber.

Remove the /hold if you're OK with it.

[creydr]

/assign @pierDipi

[creydr]

/retest

[creydr]

/test upgrade-tests

[matzew]

/lgtm
/approve

/unhold

[knative-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: creydr, matzew

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 [creydr,matzew]

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

[matzew]

/test upgrade-tests