Use new codequality docker image

Last step of gitlab-org/security-products/codequality#11 (closed)

What does this MR do?

This MR change our docker image for the codequality project used by gitlab.

Before	After
https://gitlab.com/gitlab-org/security-products/codequality/container_registry	https://gitlab.com/gitlab-org/ci-cd/codequality/container_registry

Both projects at currently at feature parity and new updates will only be made to ci-cd in the future.

The deprecation notice plan is being discussed on gitlab-org/security-products/codequality#27 (closed)

Why are we doing this?

The codequality project is now falling under the grouptesting which is why we decided to move it from the security namespace.

@drewcimino do you know if this change requires documentation ?

Screenshots

As we can see on the code_quality endpoint, the report is still reporting issues properly.

Does this MR meet the acceptance criteria?

Conformity

• Changelog entry
• [-] Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• [-] Database guides
• [-] Separation of EE specific content

Availability and Testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• [-] Tested in all supported browsers
• [-] Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• [-] Label as security and @ mention @gitlab-com/gl-security/appsec
• [-] The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• [-] Security reports checked/validated by a reviewer from the AppSec team