Instrumentation for Blame file information

What does this MR do and why?

Instrumentation added in this MR:

Events:

• click_blame_control_on_blob_page
• click_chunk_blame_on_blob_page
• click_history_control_on_blob_page
• click_ref_selector_on_blob_page
• open_blame_viewer_on_blob_page
• click_previous_blame_on_blob_page

Metrics:

• redis_hll_counters.count_distinct_user_id_from_click_blame_control_on_blob_page_monthly
• redis_hll_counters.count_distinct_user_id_from_click_chunk_blame_on_blob_page_monthly
• redis_hll_counters.count_distinct_user_id_from_click_history_control_on_blob_page_monthly
• redis_hll_counters.count_distinct_user_id_from_click_previous_blame_on_blob_page_monthly
• redis_hll_counters.count_distinct_user_id_from_click_ref_selector_on_blob_page_monthly
• redis_hll_counters.count_distinct_user_id_from_open_blame_viewer_on_blob_page_monthly

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Metric name	Monitor results
Monthly count of unique users who viewed in-file Blame on Blob page
Monthly count of unique users who navigated from specific line of code to its Blame page
Monthly count of unique users who navigated from in-file Blame viewer to see prior changes on Blame page
Monthly count of unique users who changed Git revision on Blob page
Monthly count of unique users who navigated from Blob to Commits page
Monthly count of unique users who navigated from Blob to Blame page

How to set up and validate locally

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

Related to #439361 (closed)