We need to bump binaryMinSupportedVersion to 22.2 before we release the first 23.1 beta (branch cut is currently scheduled for Feb 28).

For previous releases, we removed all older cluster version gates before bumping the binaryMinSupportedVersion. However, this doesn't need to be the case.

For this release -- in order to 1) reduce the scope of this task, and 2) distribute the task of deleting gates across the team -- we plan to instead do the following:

1. PR 1 - bump minBinary, adding skips to all the tests that fail:

   • clusterversion: bump minBinary to 22.2 #96656

2. Create tracking issue(s) for tests skipped in (1). Then assign to teams so they delete whenever.

   • disaster recovery: remove/fix tests that were ignored from bumping minBinary to V22_2 #95804
   • sql schema: remove/fix tests that were ignored from bumping minBinary to V22_2 #96751
   • storage: remove/fix tests that were ignored from bumping minBinary to V22_2 #96752

3. Rename / prefix 22.2 gates with a TODODelete_ prefix or something, so when teams see if in the code they know they can clean up related code:

   • clusterversion: rename V22_2* gates to TODODelete_V22_2* #96754

4. Create tracking issue(s) to delete 22.2 gates. Then assign to teams so they delete whenever.

   • cdc: remove V22_2 gates and related logic/migrations/etc #96762
   • disaster recovery: remove V22_2 gates and related logic/migrations/etc #96761
   • replication: remove V22_2 gates and related logic/migrations/etc #96760
   • sql sessions: remove V22_2 gates and related logic/migrations/etc #96759
   • sql observability: remove V22_2 gates and related logic/migrations/etc #96758
   • sql queries: remove V22_2 gates and related logic/migrations/etc #96757
   • sql schema: remove V22_2 gates and related logic/migrations/etc #96763
   • storage: remove V22_2 gates and related logic/migrations/etc #96764
   • kv: remove V22_2 gates and related logic/migrations/etc #96765

Jira issue: CRDB-23572