Bump Container Registry to v3.24.1-gitlab

What does this MR do?

3.24.1 (2022-02-09)

Bug Fixes

• stop creating intermediate repositories and parent/child links (f49eae4)

3.24.0 (2022-02-09)

Bug Fixes

• datastore: importer: do not pass on manifest errors (37b7db2)
• datastore: remove unnecessary transaction for manifest pre import (1dd2e30)
• datastore: repositorystore Update updates migration status (2c1e96f)
• halt (pre)import on invalid manifest referenced by list (1567594)
• halt import on tag lookup failure (c10f2e5)
• halt pre-import on tag lookup failure (002dab7)
• handlers: handle runImport error (f292acd)
• migration: parse placeholder for path in import notifier endpoint (621dc4e)
• migration: typo in import failed status (7fbd392)

Features

• datastore: use context fields for importer logging (83e783c)
• handlers: import route: return 409 conflict if repository is importing (c11fd43)
• handlers: import route: return 424 failed dependency if repository failed previous pre import (9d7c3b4)
• handlers: import route: return 425 too early if repository is pre importing (13b67de)
• handlers: metrics for API import route (55fb814)
• handlers: send import notifications (9827815)
• handlers: update repository migration status during import (062a47c)
• make the importer row count logging opt in (a1c476a)

3.23.0 (2022-01-20)

Features

• api/gitlab/v1: implement get repository details operation (d2e92b9)
• handlers: enable pre-imports via the Gitlab V1 API (967a0c9)

3.22.0 (2022-01-13)

Features

• track online migration status of repositories in the database (a18b11b)
• configuration: add tagconcurrency to migration stanza (fcc4595)
• handlers: add gitlab v1 API import route (beba40e)
• handlers: add support for tag concurrency to import API route (1bf25b3)
• handlers: send import errors to sentry (968a027)
• limit redirections to Google Cloud CDN based on a feature flag (feb1604)

Related issues

container-registry#584 (closed)

Checklist

See Definition of done.

For anything in this list which will not be completed, please provide a reason in the MR discussion

Required

• Merge Request Title, and Description are up to date, accurate, and descriptive
• MR targeting the appropriate branch
• MR has a green pipeline on GitLab.com
• Pipeline is green on dev.gitlab.org if the change is touching anything besides documentation or internal cookbooks
• trigger-package has a green pipeline running against latest commit

Expected (please provide an explanation if not completing)

• Test plan indicating conditions for success has been posted and passes
• Documentation created/updated
• Tests added
• Integration tests added to GitLab QA
• Equivalent MR/issue for the GitLab Chart opened