chore: Migrate CI/CD to GitHub Actions

[stocaaro]

Description of changes

This is the current state of the Github Actions CI/CD migration. It models the following automated processes:

• PRs run
  • unit tests
  • bundle size
• Merging to main runs:
  • unit tests
  • bundle size
  • integ/e2e tests
  • When all pass
    • Release to unstable preid
• Merging to configured preid branch runs:
  • unit tests
  • bundle size
  • integ/e2e tests
  • When all pass
    • Release to specified preid
• Merging to release branch runs:
  • unit tests
  • bundle size
  • integ/e2e tests
  • When all pass
    • Release to latest
    • Updates required-release tag if needed
    • Commits new versions and docs updates
    • Merged updates back to main branch

Patterns follows:

• Triggered workflows prefixed by the event type that triggers them.
• Callable workflow used to encapsulate reusable operations that run on isolated Github runners.
• Actions used to encapsulate code called across multiple workflows.
• All internal actions/workflows and actions referenced by relative path action and workflow.
• Use caching to reduce runtime of processes
• Prefer to test by execution - including NPM push, which is protected using verdaccio

Examples executions (for execution speed, I only ran a single RN test and ran all other tests on a single browser):

• Change builds to main releasing to unstable
• Release PR to release.
• Merge to release builds/tests/releases to latest and post-review process commits versions/docs and merges back to main.

Common actions

• How do I run integ tests for my branch?
  • Add your branch to the push-integ-test workflow and push the change to your branch.
• How do I release my changes to a preid?
  • If you've followed the pattern feat/{preid}/main, then just add your branch to the push-preid-release workflow
  • If your branch name follows a different pattern, then add it to the workflow and also update the preid passed to the npm publish workflow

Description of how you validated changes

By executing workflows, either trimmed to get to the desired condition promptly, but always rolling the whole process together and running end to end.

Checklist

• PR description included
• yarn test passes

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[ragingsquirrel3]

nit: dk if possible to combine this with push-latest-release and use the branch name as a variable, but ... also sometimes duplicating code is easier.

[stocaaro]

I get what you mean. This is closer the the pre-id workflow. For clarity, I have the different entry point workflows separated with duplicate code pushed down into callable workflows where the small amount of redundant calling adds clear entry points for users to trace forward from.

If there where problems with overlapping runs because of complex selection logic or some other driver that made a single workflow for multiple purposes better, I could get behind that. In this case, I like how simple each of these entry points are and am intentionally tuning for that.

[codecov-commenter]

Codecov Report

Merging #11638 (972c2f3) into main (f54e7c9) will not change coverage.
The diff coverage is n/a.

❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.

@@           Coverage Diff           @@
##             main   #11638   +/-   ##
=======================================
  Coverage   83.71%   83.71%           
=======================================
  Files         347      347           
  Lines       21684    21684           
  Branches     4613     4613           
=======================================
  Hits        18152    18152           
  Misses       3245     3245           
  Partials      287      287           

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[stocaaro]

As part of the security review, we have identified certain GH Action best practices that should be statically checked to ensure we keep our changes in line with the guidance / bar we have set.

This command is a static check for the practices identified.

• We should never directly embed template variables ${{ var }} in run blocks.
• We should always provide fully qualified uses references for external actions

[jimblanc]

Great work, some nits below but looks good 🔥

The yarn.lock file! 🤩

[jimblanc]

Good catch

[HuiSF]

🚀