Mono desktop CI Test jobs depend on CoreCLR artifacts but not on the build job

[jkoritzinsky]

I'm seeing this error in https://dev.azure.com/dnceng/public/_build/results?buildId=1097765:

Artifact CoreCLRProduct___Linux_arm64_release not found for build 1097765. Please ensure you have published artifacts in any previous phases of the current build.

It seems like the Mono build jobs depend on the CoreCLR product build artifacts (at least on Linux arm64), but they don't depend on the CoreCLR job finishing successfully.

[ghost]

Tagging subscribers to this area: @directhex
See info in area-owners.md if you want to be subscribed.

Issue Details

---

I'm seeing this error in https://dev.azure.com/dnceng/public/_build/results?buildId=1097765:

Artifact CoreCLRProduct___Linux_arm64_release not found for build 1097765. Please ensure you have published artifacts in any previous phases of the current build.

It seems like the Mono build jobs depend on the CoreCLR product build artifacts (at least on Linux arm64), but they don't depend on the CoreCLR job finishing successfully.

Author:	jkoritzinsky
Assignees:	-
Labels:	area-Infrastructure-mono, blocking-clean-ci
Milestone:	-

[lambdageek]

@naricc this is fixed by #62652 as well, right? Or is there more to do here?

[lambdageek]

We had to revert (in #62788) the change that untangles the Mono test jobs from CoreCLR product artifacts because while the creation of Core_Root for mono doesn't depend on the CoreCLR runtime anymore, in CI the mono runtime tests job depends on the CoreCLR product tarball because that's where the clr.hosts subset places the corerun test host.