Random CI Runs missing env vars

[mattvb91]

For some reason our current CI runs are sometimes dropping env variables we pass in as secrets. In this case its affecting our FaunaDB initialization as the secret key is missing on the running container.

Failed run
https://github.com/corejam/corejam/runs/2138006636?check_suite_focus=true#step:9:7

  env:
    SECRET_KEY: 
    GITHUB_SHA: a8798fc2e260fea2c478340897010deaf2623b99

Success run:
https://github.com/corejam/corejam/runs/2137791179?check_suite_focus=true#step:9:7

  env:
    SECRET_KEY: ***
    GITHUB_SHA: 9e48b932079767b7917bed95e7a4915376fbd3cc

No changes were made to the secrets through admin settings so this is either a github actions bug or something else?

[mattvb91]

https://github.community/t/dependabot-prs-and-workflow-secrets/163269

[mattvb91]

dependabot/dependabot-core#3253

[mattvb91]

https://docs.github.com/en/github/administering-a-repository/managing-encrypted-secrets-for-dependabot

[mattvb91]

@patrickhaug can you add the NPM secret you added for the releases on the new "dependabot" tab for secrets under settings. But make sure to add it into organization level

[patrickhaug]

We could wait for #402 and get rid of fauna ..

[mattvb91]

We will still have fauna tests tho?