Move "Patches Apply Cleanly" check to the top

[dagood]

Right now the CI results look like this when patches don't apply cleanly:

It takes several clicks to actually get from the PR screen to the pipeline and the patches step to see that that's all that went wrong.

Instead, the patches-specific check should be on top, for easier diagnosis:

Currently the checks appear to be in alphabetical order, so we might have to use an ordering trick like renaming the check to

0: Test / Patches Apply Cleanly

Comes up a lot, e.g. in submodule updates:

• Update submodule to latest master in microsoft/main #2147

A release involves a submodule update, so this improvement could help the release workflow.

[gdams]

I'd actually considered moving this check to AzDO and making it a prerequisite stage that runs before the build/test jobs? What do you think?

[gdams]

I'd actually considered moving this check to AzDO and making it a prerequisite stage that runs before the build/test jobs? What do you think?

@dagood I had a play around with this in #2150 and it seems to work pretty well. When I pushed a breaking change to the patch it renders like this:

[dagood]

• For posterity, my thoughts on eng/pipeline: add prerequisite patches check stage #2150

Unfortunately AzDO obscures the time spent waiting for an agent so it's hard to get exact numbers, but I don't like that this PR adds extra latency to every test run--an entire "wait for agent" delay that will always be on the hot path. (Let alone the ~1m of actual execution time.)