Task/add new vars for sre auth

[andrewleith]

This PR adds a new environment variable for storing the secret SRE will use to call certain API methods.

What happens when your PR merges?

• Prefix the title of your PR:
  • fix: - tag main as a new patch release
  • feat: - tag main as a new minor release
  • BREAKING CHANGE: - tag main as a new major release
  • [MANIFEST] - tag main as a new patch release and deploy to production
  • chore: - use for changes to non-app code (ex: GitHub actions)
• Alternatively, change the VERSION file - this will not create a new tag, but rather will release the tag in VERSION to production.

What are you changing?

• Releasing a new version of Notify
• Changing kubernetes configuration

Provide some background on the changes

Give details ex. Security patching, content update, more API pods etc

If you are releasing a new version of Notify, what components are you updating

• API
• Admin
• Documentation
• Document download API

Checklist if releasing new version:

• I made sure that the changes are as expected in Notify staging
• I have checked if the docker images I am referencing exist
  • api lambda (requires Notification-Production / AdministratorAccess login)
  • api k8s
  • admin
  • documentation
  • document download API

Checklist if making changes to Kubernetes:

• I know how to get kubectl credentials in case it catches on fire

After merging this PR

• I have verified that the tests / deployment actions succeeded
• I have verified that any affected pods were restarted successfully
• I have verified that I can still log into Notify production
• I have verified that the smoke tests still pass on production
• I have communicated the release in the #notify Slack channel.

[ben851]

Can you also add this (with dummy data if required) to the dev env vars?