Bump Container Registry version to v4.14.0

What does this merge request do and why?

Related to container-registry#1434 (closed)

4.14.0 (2024-11-27)

✨ Features ✨

• add option to configure TLS ciphers (38a3e89)
• bbm: add timing columns for bbm start and finish (6ed457d)
• change DB LB replica list update log entry fields (ff6af11)
• implement tag protection feature (e596e75)

🐛 Bug Fixes 🐛

• bbm: do not terminate run on transient failures (0fa69cf)
• bbm: record retrieval for ranges below batch size (ac86e54)
• consolidate log key for DB replica address (5edfe6c)
• gc/worker: ignore conn closed error (e2b1390)
• implement proper shutdown of container-registry healthchecks (1522302)
• make http check send a custom user agent (0ac5855)
• minor security issues/bugs pointed out by gosec linter (2636f56)

⚙️ Build ⚙️

• deps: update module cloud.google.com/go/storage to v1.47.0 (782eb9d)
• deps: update module github.com/schollz/progressbar/v3 to v3.17.1 (7a5ae49)
• deps: update module github.com/stretchr/testify to v1.10.0 (aa1ca72)
• deps: update module github.com/xanzy/go-gitlab to v0.113.0 (6e88fbe)
• deps: update module github.com/xanzy/go-gitlab to v0.114.0 (cc8343c)
• deps: update module golang.org/x/crypto to v0.29.0 (334149a)
• deps: update module golang.org/x/oauth2 to v0.24.0 (b3c6a75)
• deps: update module golang.org/x/time to v0.8.0 (4909774)
• deps: update module google.golang.org/api to v0.205.0 (a99cae0)
• deps: update module google.golang.org/api to v0.206.0 (3c02bc0)
• deps: update module google.golang.org/api to v0.207.0 (8873aa0)
• deps: update module google.golang.org/api to v0.209.0 (dd0af23)

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

gdk reconfigure

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.