ci: update release-schedule workflow with dynamic schedule

[joshblack]

Closes #3711

Our release schedule workflow currently runs every week and will open and close issues regardless of the settings of the current schedule that we have in PagerDuty. This PR adds in a composite action, pagerduty, that will allow us to get the current and previous schedule from the PagerDuty API and uses it in the release-schedule workflow to accurately open and close issues related to this schedule

Changelog

New

• Add pagerduty action under .github/actions/pagerduty which outputs schedule information

Changed

• Update release-schedule workflow to use new pagerduty action and correctly open/close release tracking issues for a given schedule

Removed

Rollout strategy

None

Testing & Reviewing

This is something that likely needs to be tested with workflow_dispatch to see if it's working as-intended. Ran it over in: https://github.com/primer/react/actions/runs/6316114089 with the new "dry" flag to see how it would run. Thankfully it picked up on the fact that we have an existing release issue but it was one that it couldn't identify because of how the ids are changing (now they just use the schedule id)

[changeset-bot]

⚠️ No Changeset found

Latest commit: a8383a4

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

size-limit report 📦

Path	Size
dist/browser.esm.js	104.36 KB (0%)
dist/browser.umd.js	104.94 KB (0%)

[siddharthkp]

Good stuff! Let's try it out!