Include container registry in topology pings

What does this MR do?

Refs #218546 (closed)

For the topology element in Usage Ping we are trying to ascertain which GitLab services run on which customer node. Any services that we know and can identify will be included; others will be ignored.

In the work leading up to here we covered all GitLab Omnibus services that we know to have a scrape_config so that Prometheus can target them. However, we forgot to include the container registry service. It was just an oversight. This MR fixes that.

Does this MR meet the acceptance criteria?

Conformity

• [-] Changelog entry Only new additions to the Usage Ping payload require a changelog entry. Any other changes are covered by our Privacy Policy.
• [-] 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