verify-master needs to be broken up

verify-master as a job needs to be broken up in to more specific verification checks

As verify-master runs multiple verification steps it has bucket list smell that results in
- unwieldy log output
- difficulty in assigning ownership of flake or failure
- an overall runtime of[ over an hour](https://testgrid.k8s.io/sig-release-master-blocking#verify-master&graph-metrics=test-duration-minutes)

Some of the individual checks are quite verbose a break up of the job into more specific checks would mitigate against that.

There is some pre-existing design work / discussion on-going on this @liggitt and @hasheddan
I'll add related comments and issues

This could be considered to be part of the effort documented here https://docs.google.com/document/d/1uuP9kS28u1LFyx83Yl-Sodu7-2N_exPRrEoiwbAe0wc/edit#heading=h.xgjl2srtytjt

/sig testing

Start with the verify-master job and the linked design document, then review the existing discussion and related comments from the named participants. Define separate verification checks that improve log clarity, ownership of failures, and the reported runtime; the work is done when the agreed design is implemented and those outcomes can be verified.

Written by the indexing model from the issue text.