chore(ci): introduce console SDK build checks

[JoshuaMoelans]

Introduces a workflow file that runs checks on our gaming console repos

• on each (non-forked) PR commit, we run a build for the consoles
• on each release branch, we run the full test (required check)

We use a GH app for cross-repo reporting/triggering of the action

Related console SDK PRs

Initial

• https://github.com/getsentry/sentry-playstation/pull/121
• https://github.com/getsentry/sentry-switch/pull/116
• https://github.com/getsentry/sentry-xbox/pull/114

Follow-up

• https://github.com/getsentry/sentry-switch/pull/118
• https://github.com/getsentry/sentry-xbox/pull/118
• https://github.com/getsentry/sentry-playstation/pull/124

Successful runs:

BUILD_ONLY

• PlayStation - https://github.com/getsentry/sentry-playstation/actions/runs/23855501141/job/69547250626
• Switch - https://github.com/getsentry/sentry-switch/actions/runs/23808056962/job/69387047956
• Xbox - https://github.com/getsentry/sentry-xbox/actions/runs/23845613942/job/69512041036

FULL_TEST

• PlayStation - https://github.com/getsentry/sentry-playstation/actions/runs/23855757418
• Switch - https://github.com/getsentry/sentry-switch/actions/runs/23840303557
• Xbox - https://github.com/getsentry/sentry-xbox/actions/runs/23842971831

---

TODO

• consider whether we want the full matrix on each of the consoles, since the amount of combinations might be pretty large (e.g., 6 jobs for xbox, 6 jobs for switch, 2 jobs for PlayStation), all of which are being built on one of two self-hosted windows runners which have limited resources.
  • ✅ decided with @mujacica that we can just smoke-test with a single build for each platform, and then rely on the FULL_TEST in a release branch to show breakage