Consider adding Cloud Connector as a service

Problem

We currently monitor cloud.gitlab.com as a service component of the Cloudflare service. This was implemented in !7785 (merged). Moreover, we added manual alerts for WAF events in !7787 (merged).

We should consider making Cloud Connector a first class service. This would automatically create dashboards, SLI trackers and alerts for it.

We decided against it for now because Cloud Connector is not its own entity, but rather consists of a Cloudflare reverse proxy that performs routing and rate limiting and libraries that process requests in the GitLab monolith and services upstream of the monolith who all emit their own metrics and already have dedicated SLOs.

References

• https://gitlab.com/gitlab-com/runbooks/-/blob/master/docs/uncategorized/alert-routing.md