feat: Enricher wise metrics

[laxmanchekka]

Description

We need enricher-wise metrics to identify the bottlenecks specific to enricher implementations.

Testing

Tested on a dev SaaS cluster

Checklist:

• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• Any dependent changes have been merged and published in downstream modules

[codecov]

Codecov Report

Merging #265 (84cdd20) into main (be215f0) will decrease coverage by 0.15%.
The diff coverage is 67.85%.

@@             Coverage Diff              @@
##               main     #265      +/-   ##
============================================
- Coverage     80.35%   80.20%   -0.16%     
  Complexity     1162     1162              
============================================
  Files           102      102              
  Lines          4506     4512       +6     
  Branches        420      421       +1     
============================================
- Hits           3621     3619       -2     
- Misses          688      695       +7     
- Partials        197      198       +1     

Flag	Coverage Δ
unit	80.20% <67.85%> (-0.16%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
...trace/enricher/StructuredTraceEnrichProcessor.java	88.88% <ø> (-4.30%)	⬇️
.../traceenricher/enrichment/EnrichmentProcessor.java	74.35% <67.85%> (-3.83%)	⬇️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update be215f0...84cdd20. Read the comment docs.

[avinashkolluru]

nit: We can get rid of the hypertrace. prefix in both the metric names

[laxmanchekka]

This is the metric convention we are using across hypertrace projects.
Also, this may cause compatibility issue if we change the name and existing dashboards may be broken.

@kotharironak @rish691: please confirm if changing and simplifying this metric name is okay?

[kotharironak]

It is exposed in ready to use dashboard - https://github.com/hypertrace/hypertrace/tree/main/kubernetes/monitoring/dashboards. So would suggest keeping it as is now. And, we can clean up if we decided to go with metrics.reporter based prefix only in application.conf

[github-actions]

Unit Test Results

  70 files  ±0    70 suites  ±0   56s ⏱️ -1s
379 tests ±0  379 ✔️ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit dd0a5fb. ± Comparison against base commit be215f0.