[Remote Store Migration] Handling translog metadata update during remote store migration

[shourya035]

Description

Wiring RespositoriesService to IndexMigrationUpdater from ClusterModule through AllocationService. This is being utilized during remote store migration flow to determine if the translog repository supports the newly introduced tlog metadata in object metadata feature #13091

Related Issues

Resolves #13745

Check List

• New functionality includes testing.
  • All tests pass
• New functionality has been documented.
  • New functionality has javadoc added
• API changes companion pull request created.
• Failing checks are inspected and point to the corresponding known issue(s) (See: Troubleshooting Failing Builds)
• Commits are signed per the DCO using --signoff
• Commit changes are listed out in CHANGELOG.md file (See: Changelog)
• Public documentation issue/PR created

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[github-actions]

❌ Gradle check result for e09d1f8: 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 c00a803: 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 7d7dd50: 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 b470ddb: 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 ea8de1f: 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

Attention: Patch coverage is 65.38462% with 9 lines in your changes are missing coverage. Please review.

Project coverage is 71.67%. Comparing base (b15cb0c) to head (eea6ff7).
Report is 335 commits behind head on main.

Files	Patch %	Lines
.../org/opensearch/index/remote/RemoteStoreUtils.java	53.84%	2 Missing and 4 partials ⚠️
.../cluster/routing/allocation/RoutingAllocation.java	62.50%	0 Missing and 3 partials ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##               main   #13810      +/-   ##
============================================
+ Coverage     71.42%   71.67%   +0.25%     
- Complexity    59978    61313    +1335     
============================================
  Files          4985     5065      +80     
  Lines        282275   288144    +5869     
  Branches      40946    41723     +777     
============================================
+ Hits         201603   206535    +4932     
- Misses        63999    64515     +516     
- Partials      16673    17094     +421     

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

[github-actions]

❌ Gradle check result for e176d48: 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 23549ad: 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 eea6ff7: SUCCESS

[gbbafna]

We are not planning for this change anymore. Closing it .