Stop running both normal and no_tiered_compilation scenarios for coreclr PRs

[jakobbotsch]

This changes innerloop/outerloop test groups to run only in the no_tiered_compilation scenario on PRs, as discussed in #69122.

[ghost]

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

Issue Details

---

This changes innerloop/outerloop test groups to run only in the no_tiered_compilation scenario on PRs, as discussed in #69122.

Author:	jakobbotsch
Assignees:	-
Labels:	area-Infrastructure-coreclr
Milestone:	-

[jakobbotsch]

Will need to verify that it is still possible to trigger some TC testing on PRs and otherwise provide a way to do it.

[jakobbotsch]

Success -- the automatically triggered runtime run submitted only Helix jobs in no_tiered_compilation for the runtime tests.

I've also manually triggered a runtime run from AzDO that points at refs/pull/69178/head and that properly ends up using the fuller matrix (which, among other things, still runs scenarios with both TC on and off). So testing TC changes in PRs can be done that way. Requesting other non-innerloop/outerloop pipelines that disable/enable TC should also not be affected by the change.

I opened #69192 for the installer failure and the osx-x64 test failure is known as well. PTAL @dotnet/runtime-infrastructure

cc @kouvel @jkotas @janvorli for awareness of the above.

[jakobbotsch]

Also cc @dotnet/jit-contrib for awareness of the above -- automated runtime runs on PRs will no longer run coreclr tests with TC enabled, so for PGO related changes make sure to trigger the PGO pipelines and/or the runtime job in the way I specified above.

[jakobbotsch]

@trylek @hoyosjs @jkotas it would be nice to merge this before activity starts picking up today, can one of you approve?

[jkotas]

Thank you!