cluster_bootstrap_tests test upgrade 22.2 -> 22.3, not -> newest

[dlex]

This is to avoid skipping major versions in upgrade tests

Re #7310

Backports Required

• none - not a bug fix
• none - issue does not exist in previous branches
• none - papercut/not impactful enough to backport
• v22.3.x
• v22.2.x
• v22.1.x

UX Changes

• none

Release Notes

• none

[andrwng]

I don't think this is the right approach. A test that doesn't actually test dev doesn't serve much purpose, and we might as well just remove the test entirely, since it already exists and gets run in the v22.3.x branch. If anything, perhaps we should make the test walk through a series of upgrades, verifying the various invariants (that a cluster UUID exists, etc) between each.

[dlex]

Agree, it makes sense changing it in the way to upgrade to 22.3.latest, backport to 22.3 and then delete from dev.