Bump gcs version to fix failing pipeline

What does this MR do?

The issue described by Investigate failing custom-ca jobs in secure-te... (gitlab-org/gitlab#415134 - closed) was fixed in Pin build scripts to use docker:24-dind [4.x] (!2892 - merged), however, the trigger-db-update scheduled pipeline is still building container scanning images for the tag 4.6.23 which doesn't have this fix, and this is causing failures.

This MR bumps the version for Container Scanning on the v4.x branch so that we create a new tag, which will allow the trigger-db-update scheduled pipeline to succeed. See this thread for more details.

What are the relevant issue numbers?

Investigate failing custom-ca jobs in secure-te... (gitlab-org/gitlab#415134 - closed)

Does this MR meet the acceptance criteria?

• [-] Changelog trailer added
• Documentation created/updated for GitLab EE, if necessary
• Documentation created/updated for this project, if necessary
• Documentation reviewed by technical writer or follow-up review issue created
• Tests added for this feature/bug
• Job definition updated, if necessary
  • Auto-DevOps template
  • Job definition example
  • CI Templates
• Conforms to the code review guidelines
• Conforms to the Go guidelines
• Security reports checked/validated by reviewer