Fix runtime-staging trigger and one bug

[akoeplinger]

We were triggering the runtime-staging jobs for all branches rather than just PRs and the scheduled runs on main.
Fix it to only run for pushes on release branches, like runtime.yml.

I also noticed a small bug where we had interpreter: true in the "iOS/tvOS devices - Full AOT + AggressiveTrimming" job, that was probably a copy/paste mistake.

[ghost]

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

Issue Details

---

We were triggering the runtime-staging jobs for all branches rather than just PRs and the scheduled runs on main.
Fix it to only run for pushes on release branches, like runtime.yml.

I also noticed a small bug where we had interpreter: true in the "iOS/tvOS devices - Full AOT + AggressiveTrimming" job, that was probably a copy/paste mistake.

Author:	akoeplinger
Assignees:	-
Labels:	area-Infrastructure-libraries
Milestone:	-

[ViktorHofer]

Hmm the Fuzzlyin pipeline also runs on every PR, presumably because of #59657. Would you mind also taking care of it?

@kunalspathak

[akoeplinger]

@ViktorHofer it's not running on every PR, just this one because I pushed a branch to the dotnet/runtime repo and not my fork and it is missing the trigger key too, like runtime-staging. Will fix.

[akoeplinger]

Actually, is that pipeline supposed to be running on-demand via a comment trigger on PRs only? In that case we need to change an AzDO setting.

[akoeplinger]

I set the "Require a team member's comment" setting in AzDO for the Fuzzlyn pipeline:

[kunalspathak]

This pipeline is still in progress ...I will disable it for now. Sorry for the confusion.

[akoeplinger]

@kunalspathak with the current settings it should only be triggered via an explicit /azp run command so no need to explicitly disable it :)