"ci_jwt_signing_key" needs to be configured in all GitLab environments

When gitlab-org/gitlab!34249 (merged) landed in staging, the Kubernetes deploy had failed. It failed due to us centrally managing all secrets for our .com infrastructure. When this secret was failed to be found in our configuration, GitLab attempts to generate one. In Kubernetes land, this fails as the secret file that contains all the secrets is centrally managed and is mounted as a read only file inside of the Pod. For ominbus installations, this causes every server to generate it's own unique token. This causes a large problem as when a user reaches out to the server with the request that is encrypted with that token, that data cannot be read successfully by any other server.

Utilize this issue to work with @krasio on issue gitlab-org/gitlab#214607 (closed) to ensure that prior to the next attempt at merging this feature in, all environments for GitLab are ready to go. This will require that Infrastructure generates and configures a new token ready to be utilized by rails.