[mono] Create separate yml that can trigger full test runs on demand

[steveisok]

Since a large share of the mono configurations are now running only smoke tests on each PR, we need to have a way to manually trigger running all tests. A copy of runtime.yml that can only be manually triggered is probably the easiest option, but I'm sure there are others.

An engineer should be able to trigger a full test run via /azp run <yet-to-be-named.yml>

[dotnet-issue-labeler]

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[ghost]

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

Issue Details

---

Since a large share of the mono configurations are now running only smoke tests on each PR, we need to have a way to manually trigger running all tests. A copy of runtime.yml that can only be manually triggered is probably the easiest option, but I'm sure there are others.

An engineer should be able to trigger a full test run via /azp run <yet-to-be-named.yml>

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

[radical]

Can it be nested like mono.yml can contains apple/android/wasm.yml, and any further splits, if useful. And these can be triggered on-demand. then maybe runtime.yml can use the above mono.yml?

[akoeplinger]

Yeah you can nest templates, basically like we use the eng/pipelines/common/platform-matrix.yml template in runtime.yml which in turn uses the xplat-setup.yml and so on.

[steveisok]

The jobs can now be triggered via /azp run runtime-manual as a result of #61641