ci: Reduce the number of tokens we use

What does this MR do and why?

• GITLAB_QA_MR_ALLURE_REPORT_TOKEN and PROJECT_TOKEN_FOR_CI_SCRIPTS_API_USAGE are both https://gitlab.com/gitlab-org/gitlab project access tokens as explained at gitlab-org/quality/engineering-productivity/team!56 (diffs)
• GITLAB_QA_PRODUCTION_ACCESS_TOKEN and QA_GITLAB_CI_TOKEN are both @gitlab-qa's tokens used for CI-related actions as explained at gitlab-org/quality/engineering-productivity/team!56 (diffs)
  • Note that we're still using this variable in https://ops.gitlab.net/groups/gitlab-org/quality/-/settings/ci_cd => https://gitlab.com/gitlab-org/quality/pipeline-common/-/blob/653abee5162bd68b93bfb761f311d0a0a14211a7/ci/dot-com/reports.gitlab-ci.yml#L41 so we cannot get rid of the token itself.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.