Staggered merges metrics

[Sukriti0717]

Implemented a comprehensive metrics framework that captures 8 key metrics across node-level and shard-level operations:

1. Total scheduler execution time
2. Total Merges Triggered
3. Total Merges Skipped
4. Skips count due to Node Validator
5. Total failed force merges
6. Shard specific
   1. Time taken by force merge
   2. Shard size
   3. Segment count

[github-actions]

❌ Gradle check result for b8527b9: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❕ Gradle check result for 42b7925: UNSTABLE

Please review all flaky tests that succeeded after retry and create an issue if one does not already exist to track the flaky failure.

[codecov]

Codecov Report

❌ Patch coverage is 98.38710% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 72.97%. Comparing base (6fdb010) to head (56bee61).
⚠️ Report is 2 commits behind head on main.

Files with missing lines	Patch %	Lines
...ch/index/autoforcemerge/AutoForceMergeManager.java	97.05%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##               main   #19226      +/-   ##
============================================
+ Coverage     72.90%   72.97%   +0.06%     
- Complexity    69915    69916       +1     
============================================
  Files          5675     5676       +1     
  Lines        320841   320923      +82     
  Branches      46387    46392       +5     
============================================
+ Hits         233909   234189     +280     
+ Misses        68031    67786     -245     
- Partials      18901    18948      +47     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[github-actions]

❌ Gradle check result for 440b472: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for 440b472: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for 9735956: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

✅ Gradle check result for a81b1df: SUCCESS

[github-actions]

❌ Gradle check result for fef6db0: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for fef6db0: null

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for fef6db0: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for fef6db0: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

✅ Gradle check result for 56bee61: SUCCESS