Optimize GitHub Actions PR Triage Scheduler Frequency

[Han5991]

Current Issues:

• Fork pollution: The scheduler runs in every fork of the repository, creating unnecessary load across the GitHub ecosystem
• Resource waste: Runs even when there are no new PRs or changes to existing PRs
• API rate limiting risk: Frequent GitHub API calls may hit rate limits unnecessarily
• Workflow noise: Creates excessive workflow run history that's hard to navigate

[swissspidy]

Makes sense to me. Ideally it shouldn't need to run on a schedule though, but that's for another day.

[jackwotherspoon]

Already an open PR for this: #3093