Bump container registry to v4.6.0-gitlab

What does this merge request do and why?

Upgrades the container registry to v4.6.0-gitlab

It is a big upgrade https://gitlab.com/gitlab-org/container-registry/-/blob/master/CHANGELOG.md but we should try to update it in one go. There are some breaking changes but I expect it won't affect many people as the changes are very specific https://gitlab.com/gitlab-org/container-registry/-/blob/master/CHANGELOG.md#-breaking-changes

Related to Release Version v4.6.0-gitlab (container-registry#1290 - closed)

How to set up and validate locally

1. Follow https://gitlab.com/gitlab-org/gitlab-development-kit/-/blob/main/doc/howto/registry.md?ref_type=heads#set-up-pushing-and-pulling-of-images-over-http
2. gdk tail registry
3. Verify the version

2024-07-05_06:14:41.83248 registry              : {"go_version":"go1.22.4","instance_id":"3422c198-cc89-40b7-98a2-0e951d475444","level":"info","msg":"Starting upload purge in 27m0s","time":"2024-07-05T06:14:41.866Z","version":"v4.6.0-gitlab"}
2024-07-05_06:14:41.84205 registry              : {"go_version":"go1.22.4","instance_id":"3422c198-cc89-40b7-98a2-0e951d475444","level":"info","msg":"listening on [::]:5000","time":"2024-07-05T06:14:41.880Z","version":"v4.6.0-gitlab"}

"version":"v4.6.0-gitlab" matches this upgrade 🎉

Impacted categories

The following categories relate to this merge request:

• gdk-reliability - e.g. When a GDK action fails to complete.
• gdk-usability - e.g. Improvements or suggestions around how the GDK functions.
• gdk-performance - e.g. When a GDK action is slow or times out.

Merge request checklist

• This change is backward compatible. If not, please include steps to communicate to our users.
• Tests added for new functionality. If not, please raise an issue to follow-up.
• Documentation added/updated, if needed.
• Announcement added, if change is notable.
• gdk doctor test added, if needed.
• Add the ~highlight label if this MR should be included in the CHANGELOG.md.