ci: Use new SENTRY_AUTH_TOKEN for CI requests

Doing it this way will allow us to transparently switch over without
worrying about mixing up the keys.

Signed-off-by: Kristofer Rye <[email protected]>

Author: rye

.github/workflows/analyze-and-build.yml

@@ -56,7 +56,7 @@ jobs:
           FASTLANE_DISABLE_ANIMATION: '1'
           SENTRY_ORG: frog-pond-labs
           SENTRY_PROJECT: all-about-olaf
-          SENTRY_AUTH_TOKEN: ${{ secrets.SENTRY_AUTH_TOKEN }}
+          SENTRY_AUTH_TOKEN: ${{ secrets.HOSTED_SENTRY_AUTH_TOKEN }}
           GITHUB_KEYS_REPOSITORY_TOKEN: ${{ secrets.GITHUB_KEYS_REPOSITORY_TOKEN }}
 
   ios:
@@ -83,7 +83,7 @@ jobs:
           FASTLANE_DISABLE_ANIMATION: '1'
           SENTRY_ORG: frog-pond-labs
           SENTRY_PROJECT: all-about-olaf
-          SENTRY_AUTH_TOKEN: ${{ secrets.SENTRY_AUTH_TOKEN }}
+          SENTRY_AUTH_TOKEN: ${{ secrets.HOSTED_SENTRY_AUTH_TOKEN }}
           GITHUB_KEYS_REPOSITORY_TOKEN: ${{ secrets.GITHUB_KEYS_REPOSITORY_TOKEN }}
       - run: yarn detox build e2e --configuration ios.sim.release | xcpretty
       - run: yarn detox test e2e --configuration ios.sim.release --cleanup