Deploy with GH Pages

[emplums]

Description

This PR moves our preview deploys from Now/vercel to GH Pages via an amazing action that I copypasta'd from @lerebear 's work! 🙌 🎉 Huge shoutout to Lere for coming up with these workflows!

I've also built an action for deploying our docs to the production url (https://primer.github.com/components). I tested it by changing the action to run on pushes to this branch and it worked smoothly and deployed here: https://primer.github.io/components (note that contributor data doesn't show up, but i fixed that in a later commit)

Notes

I needed to use a personal access token in the request_deployment workflows because jobs using the GITHUB_TOKEN are prevented from triggering other workflows as Lere pointed out in his original PR

Rollout Plan

• Merge this PR and make sure deploys on pushes to master works
• Test that a path alias in primer.style pointing to a non-vercel deploy works okay. I don't see anything in the vercel docs that says otherwise so I think it should be fine, but to test carefully we could set up a route like this:
  {"src": "/test-components(/.*)?", "dest": "https://primer.github.com/components"},
• Remove the vercel integration on this repository
• Migrate over other repositories. See migration for other repos below

To do:

• URLs off the root are not resolving correctly
• Animation in hero is not displaying
• Add seperate job for deploying to production
• Contributions isn't working - I noticed in the deploy to production action that the script output this error Non-deploy build and no GITHUB_TOKEN environment variable set; skipping GitHub API calls. the GITHUB_TOKEN environment variable should be set so I need to see if there's some way that this script classifies something as a deploy/non-deploy build fixed this just for production builds so we don't have to wait for all the API calls for each deploy preview. need to double check that it worked after merging to master

Migration Plan for Other Repos

• Add a personal staging deployment token to repo
• Copy over workflow files
• Update name, repo, environment_url in deploy-to-gh-pages.yml
• Update name, environment_url, and repo in deploy-to-staging.yml
• Update repo and description in request-staging-deployment.yml
• Update pathPrefix in gatsby-config.yml

Possible Improvements

• Might be able to clean up the code a bit and have one file for requesting deploys & one file for doing deployments and separate steps with if parameters for each environment?

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/primer/primer-components/akz4lzv8s
✅ Preview: https://primer-components-git-preview-deploys.primer.vercel.app

[emplums]

This makes it so that urls work with the weird staging deploy URLs

[emplums]

Closing this for now - I've written up some thoughts on why this doesn't feel like the best approach right now here: https://docs.google.com/document/d/1FImxLWEwKslz_Tu6s-3QXifSHqaX4_2UP2q9Gixb6gE/edit?usp=sharing

Unfortunately I needed to discuss some confidential stuff in the doc so the sharing is set to only GH employees, if anyone has any questions though feel free to ask here and I will try to answer! 😄