re-introduce sentry config' on containerized-pipelines.

implementation

• in app-interface, port the Sentry auth-token from the current job-template to the new one ("build-master").
  this token is grabbed from the env' during jenkins builds (see push_to_insights.sh), where it's defined as $GLITCHTIP_TOKEN (see our job-templates @ app-interface). this env-var becomes available with the attachment of the uhc_insights_platform secret to the job-template.
• adapt uhc-portal's build accordingly: port the strategy used in push_to_insights.sh and introduce the sentry-version and sentry-project to the SaaS build flow, in order to build source-maps and publish them.

acceptance testing

changes to deployment-pipelines can only be tested after being merged to master 🤷

once changes are merged, the test-plan is:

verify sourcemaps build

• after the (latest) MR which fixes this ticket had been merged, grab its merge-commit (but only the first 7 chars!), and wait for its build-master jenkins-run to complete (while you're at it, check the log to verify that sourcemaps:... commands are executed)
• grab the corresponding master image-tag from our Quay repo (i.e. a tag either in the form <hash> or <hash>-single, but not pr-<pr_id>-<hash>), or a later one from master
• pull its image locally & run it in a container, using Podman or whatever
• get into the container's terminal, and search for evidence inside the build-artifacts' contents (replace <image-tag> with your chosen tag):

  grep -R 'ocm-uhc-portal-stage' dist/stable  # <-- this should yield some output
  grep -R 'ocm-uhc-portal-stage' dist/preview  # <-- this should yield no output
  grep -R <image-tag> dist/stable  # <-- this should yield some output
  grep -R <image-tag> dist/preview  # <-- this should yield a single line of unrelated output, from /app.info.json#src_hash
  

verify sourcemaps release

• log into glitchtip console, and visit the uhc-portal staging project releases page.
  make sure there's a published release baring the same <hash> as the quay image-tag actually, the version should be a longer hash which matches the SENTRY_VERSION created during build
• drill down to ensure that release contains sourcemap files (i.e. not empty)