feat: Separate CI jobs into workflows

[bitsandfoxes]

Addresses the first part of #1975

This separates the jobs that were targeting multiple platforms into individual workflows, responsible for a singular purpose. I.e.

1. platform-smoke-test-build
2. platform-smoke-test-compile
3. platform-smoke-test-run

The restructuring of jobs also netted a nice speed increase from 55 down to about 30 minutes.
I.e.

• Creating the empty smoke test project right from the beginning
• Having the job that installs the sentry package go through all of the setup required and then only wait for the UPM to be available to download while the SDK is building.

#skip-changelog

[github-actions]

	Messages
📖	Do not forget to update Sentry-docs with your feature once the pull request gets approved.

Generated by 🚫 dangerJS against 383acb1

[vaind]

Looks pretty good to me although I'm not a fan of duplicating the "*-smoke-test-build" from a single place (although with a couple of platform checks) to separate workflows. If this is about moving to a separate workflow file, maybe consider doing so but keeping a single copy. Alternatively, it could make sense to group the common set of subsequent steps to a single composite action.

[vaind]

Another unrelated one: maybe worth tracking this as well to add 2022 and 6000?

[bitsandfoxes]

Fair enough. The resulting artifacts are not usable for distribution but we could at least check whether it builds?

[bitsandfoxes]

Looks pretty good to me although I'm not a fan of duplicating the "*-smoke-test-build" from a single place (although with a couple of platform checks) to separate workflows. If this is about moving to a separate workflow file, maybe consider doing so but keeping a single copy. Alternatively, it could make sense to group the common set of subsequent steps to a single composite action.

I'm splitting the changes into smaller, more digestible steps. I'm following up on the *-smoke-test-compile/smoke
in #1993 and merge build and compile into one, relying on Unity's environment instead of trying to recreate a working setup in a new job.

I'm more than happy to extract and compose this into composite actions once I get it working.

[vaind]

LGTM and I'm fine with followups in separate issues/PRs