Bump container registry to v3.86.1-gitlab (pre/gstg)

What does this MR do?

Related to gitlab-org/container-registry#1155 (closed)

NOTE:

We have labeled the pgx dependency upgrade as a high-risk-change. The library has been updated to a major upgrade that contains certain performance changes. We sided on being extra cautious for this change so that we can revert quickly in case things go south. Please follow the updated reviewer checklist.

Changelog

3.86.1 (2023-11-08)

⚙️ Build ⚙️

• deps: update module github.com/spf13/viper to v1.17.0 (9d1659f ( gitlab-org/container-registry@9d1659f0))
• deps: upgrade github.com/jackc/pgx driver to latest v5 (d9769f8 ( gitlab-org/container-registry@d9769f8a))

Author Check-list

Please read the Contributing document and once you do, complete the following:

• Check if all of the following apply:
  • Assign to the correct reviewer per the contributing document
  • Apply the correct metadata per the contributing document
  • Link to related MRs for applying the changes on other environments
  • Link to related Chef changes
  • If necessary link to a Criticality 4 Change Request issue

Reviewer Check-list

• Note this is a high-risk-change, please follow the list after deploying.
  • Check the #qa-staging Slack channel for staging end-to-end tests passed!. Make sure the corresponding pipeline started after the registry deployment completed. Otherwise, wait for the next one. https://gitlab.slack.com/archives/CBS3YKMGD/p1699489841811889
  • Check logs for errors.
  • Check metrics dashboard.
• Check if all of the following apply:
  • Reviewed the diff jobs to confirm changes are as expected
  • No changes shown in the diffs not associated with this MR - This may require a rebase or further investigation

Applier Check-list

• Make sure there is no ongoing deployment for the affected envs before merging (see #announcements slack channel)