The release/latest version marker will stay on 1.23.0-alpha.0 until another 1.23 pre-release is tagged which isnt for a while.
This will skip the MetricsGrabber test for that tag which has been fixed in master. Once a new 1.23 pre-release has been tagged we can remove this.
Alternatively we migrate all jobs off of the release/latest version marker since it isn't particularly valuable.
The fix won't make it into 1.22.0, instead slated for 1.22.1.
To avoid additional jobs failing (those that use release/stable k8s version marker) we can ignore the test now that the issue is known and the fix is ready to be merged.
This will move the logic from build_jobs.py into kubetest2 itself.
This way we can rely on this logic from scenario scripts and other places that arent directly set by build_jobs.py.