Add Internal Event Tracking for ci_build_minutes

Problem to solve

Currently, we only track runner usage for GitLab.com customers tracking ci_build_minutes in Snowflake.

We want to use it to gain visibility on all runner usage (instance, group & project runners) across subscription models (.com, Dedicated, self-managed), to understand the usage and growth of usage of runners.

One of the key motivators is Hosted runner usage estimation (gitlab-com/gl-infra/gitlab-dedicated&515 - closed) • Unassigned, where we need to https://gitlab.com/gitlab-com/gl-infra/gitlab-dedicated/team/-/issues/6174+.

Proposal

Use Internal event tracking as the predecessor of service ping, to track runner usage (instance, group & project runners) across subscription models (.com, Dedicated, self-managed).