Periodically update container registry type settings

What does this MR do?

This is related to #204839 (closed). We want to be able to determine the type (GitLab Container Registry or a third-party one) and the version of the container registry used by a self-managed instance in order to drive future prioritization and user-experience decisions.

To do this we need to implement a periodical refresh of the stored information about the container registry in order to account for a possible change. This is implemented using a cron job which calls the UpdateContainerRegistryInfoService service. The cron job is set to run once per day at midnight.

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

Related to #204839 (closed)