Store auth tokens for various APIs

[chrisolsen-goa]

We have a number of auth tokens, created by different people, use in various places. We need to better manage the tokens, which will provide us with later knowledge of which tokens are actually being used and where.

One example to where this would be useful is that non-legacy tokens, which should be used if they can, require expiration dates. Being able to easily know which tokens are expiring when would be nice.

Acceptance Criteria

1. Document Tokens in Confluence
   • Description of each token and what it's for
   • Type of token
   • Add expiry of each token (talk to @chrisolsen to determine the expiry date)
2. Remake VITE_AUTH_TOKEN used in ui-components-docs to be fine-grained and have an expiration
3. Delete unused tokens and environment secrets

[twjeffery]

This issues is needed for this update to the design system website to show issue counts from Github per component: https://github.com/GovAlta/ui-components-docs/pull/337

Deploy preview

[dustin-nielsen-goa]

@twjeffery Use the VITE_AUTH_TOKEN for Github authorization. Let me know if we need more permissions.