Mono CI Utilization Improvements

[steveisok]

Starting with #60727, we have scaled back the amount of mono tests run per PR. This issue tracks additional follow up work & potential future enhancements.

• Create separate yml that can trigger full test runs on demand
• Detect changes in library projects and run them as part of the smoke test (e.g. a change in System.Collections runs its tests)
• Apply changes to apple mobile configurations after Bring up full library test CI runs on iOS / tvOS devices #59503 lands
• Allow developers to provide parameters (e.g a list of library suites to run) when manually triggering builds
• Move most / all of runtime staging legs to the runtime pipeline (runtime-extra-platforms)
• Create bisect scripts or targets that help with post PR failures

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

Issue Details

---

Starting with #60727, we have scaled back the amount of mono tests run per PR. This issue tracks additional follow up work & potential future enhancements.

• Create separate yml that can trigger full test runs on demand
• Apply changes to apple mobile configurations after Bring up full library test CI runs on iOS / tvOS devices #59503 lands
• Allow developers to provide parameters (e.g a list of library suites to run) when manually triggering builds

Author:	steveisok
Assignees:	-
Labels:	untriaged, area-Infrastructure-mono
Milestone:	-

[safern]

Create separate yml that can trigger full test runs on demand

maybe some of the legs in these optional yaml should run always based on path changes?

[akoeplinger]

maybe some of the legs in these optional yaml should run always based on path changes?

Yeah though I think I'd prefer extending evaluate-changed-paths.sh so that it outputs more fine grained variables that we can use in runtime.yml to trigger the full runs.

[safern]

Yeah though I think I'd prefer extending evaluate-changed-paths.sh so that it outputs more fine grained variables that we can use in runtime.yml to trigger the full runs.

Yeah that'd be great. The infra should already support more variables, we would just need to add extra entries on the yml include/exclude paths parameter to the script.