Change superpmi-replay pipeline from PR triggered to scheduled

[BruceForstall]

No description provided.

[Copilot]

Pull Request Overview

This PR changes the trigger for the superpmi-replay pipeline from being PR triggered to running on a daily schedule.

• Replaced the PR trigger with a scheduled run using a cron expression
• Removed path filtering to enable the pipeline to run consistently on the main branch

[Copilot]

Consider clarifying the timezone conversion between the cron expression '0 7 * * *' (UTC) and the displayName 'Daily at 11:00 PM (UTC-8:00)' in a comment to make the intended schedule more explicit.

[dotnet-policy-service]

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

[BruceForstall]

As we've discussed internally, the superpmi-replay job does a lot of JitStressRegs variations that are not useful for every PR. The "baseline" run it does simply duplicates the runs done as part of superpmi-diffs. So, to save resources, change the replay job from triggered on PR to daily scheduled. Also, it will be manually triggerable as desired.

I believe to make this actually work, the "Require a team member's comment before building a pull request" checkbox in the UI configuration on the pipeline needs to be checked after this PR is merged.

@jakobbotsch @kunalspathak @dotnet/jit-contrib PTAL

[kunalspathak]

LGTM. Should we update our documentation to also monitor the status of this pipeline every week now? Earlier the PR author would do this.