[mono][infra] Refactor running condition for runtime-ioslike and runtime-llvm pipelines

[matouskozak]

After setting up automatic runs of runtime-ioslike and runtime-llvm pipelines on PRs that touch Mono AOT-llvm code (#111614), un unwanted side effect appeared that the pipelines don't run on PRs that do not touch the selected files, even when triggered manually by comment.

To work around this, I've reverted the previous change and instead included the runtime-extra-platforms-ioslike.yml and runtime-extra-platforms-llvm.yml (previously runtime-llvm.yml) inside the runtime.yml and conditioned them by

or(
or(eq(variables['isiOSLikeOnlyBuild'], true), eq(variables['isExtraPlatformsBuild'], true)),
and(eq(variables['isRollingBuild'], false), eq(stageDependencies.EvaluatePaths.evaluate_paths.outputs['SetPathVars_mono_aot_llvm.containsChange'], true))

This allows to:

1. run via runtime-ioslike or runtime-extra-platforms
2. run automatically on PRs when Mono AOT-llvm code changes

and similarly for runtime-llvm and runtime-extra-platforms-llvm

I also removed Mono AOT-llvm jobs from runtime.yml as they are now included via runtime-extra-platforms-llvm.yml.

---

Before merging this PR we should:

• Disable the automatic runs of runtime-llvm and runtime-ioslike which we enabled after [mono] Run runtime-llvm and runtime-ioslike on Mono LLVM PRs #111614.
• Verify effects of Unify main and app output logs to improve the UX of failure investigation xharness#1348 on Build Analysis tracking and ensure all added jobs are green or properly tracked by Build Analysis.

[dotnet-policy-service]

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

[Copilot]

Copilot reviewed 5 out of 7 changed files in this pull request and generated no comments.

Files not reviewed (2)

• eng/pipelines/common/variables.yml: Evaluated as low risk
• eng/pipelines/runtime-ioslike.yml: Evaluated as low risk

[matouskozak]

During offline discussion, it was suggested that it might be worth considering returning to behavior #111614 where runtime-ioslike and runtime-llvm pipeline were only executed when triggered by /azp run comment.

@steveisok @akoeplinger @kotlarmilos @ivanpovazan
I would like to know you opinion on whether this PR should go through or return the original before is preferred. I think that both options are viable and have their advantages and disadvantages.

Current behavior:

• [+] runtime-ioslike and runtime-llvm are executed automatically on PRs modifying Mono AOT LLVM code
• [-] runtime-ioslike and runtime-llvm cannot be executed manually by commenting on PRs NOT modifying Mono AOT LLVM code

Original behavior:

• [+] runtime-ioslike and runtime-llvm can only be executed manually by commenting on any PR
• [-] contributors must be aware that they must execute these two pipelines on PRs modifying Mono AOT LLVM code to ensure proper test coverage

This PR:

• [+] runtime-extra-platforms-ioslike and runtime-extra-platforms-llvm inner jobs are executed automatically on PRs modifying Mono AOT LLVM code
• [+] runtime-ioslike and runtime-llvm can only be executed manually by commenting on any PR
• [-] added new complexity to the yaml files