Migrate analytics_unique_visits to use Metric Instrumentation class

What does this MR do and why?

Describe in detail what your merge request does and why.

Resolves #339317 (closed)

Move 21 events (20 active and 1 removed) and 2 totals of analytics redis hll source to instrumentation class

Screenshots or screen recordings

These are strongly recommended to assist reviewers and reduce the time to merge your change.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

1. Generate service ping payload data

   data = ServicePing::BuildPayload.new.execute

2. Verify that data contains all the required analytics keys

   data["analytics_unique_visits"]
   => {
   "g_analytics_productivity"=>0,
   "p_analytics_issues"=>0,
   "p_analytics_code_reviews"=>0,
   "g_analytics_insights"=>0,
   "g_analytics_issues"=>0,
   "p_analytics_merge_request"=>0,
   "p_analytics_insights"=>0,
   "g_analytics_contribution"=>0,
   "g_analytics_valuestream"=>0,
   "users_viewing_analytics_group_devops_adoption"=>0,
   "p_analytics_ci_cd_lead_time"=>0,
   "i_analytics_cohorts"=>0,
   "p_analytics_repo"=>0,
   "p_analytics_ci_cd_deployment_frequency"=>0,
   "p_analytics_pipelines"=>0,
   "p_analytics_ci_cd_pipelines"=>0,
   "i_analytics_instance_statistics"=>0,
   "analytics_unique_visits_for_any_target"=>0,
   "i_analytics_dev_ops_score"=>0,
   "p_analytics_valuestream"=>0,
   "i_analytics_dev_ops_adoption"=>0,
   "analytics_unique_visits_for_any_target_monthly"=>0
   }

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.