[Remote Segment Store] Add Lucene major version to UploadedSegmentMetadata

[BhumikaSaini-Amazon]

Description

This PR associates the Lucene major version with each uploaded segment file metadata entry that is maintained in remote store. As part of the Lucene version compatibility check, this major version information stored in the metadata will be used to skip downloading the segment files unnecessarily if they were written by an incompatible Lucene version.

1. For the segment files that house the segment data (.cfe, .cfs, etc.), we track the Lucene major version as captured in the respective SegmentInfo instance.

2. For the segment_N files that house the information on segments, we track the Lucene major version used for the commit as captured in the respective SegmentInfos instance.

3. For the _<segmentNumber>_<monotonicallyIncrementingCountOfUpdate>_Lucene<major><minor>_<bugfix>.dvm, _<segmentNumber>_<monotonicallyIncrementingCountOfUpdate>_Lucene<major><minor>_<bugfix>.dvd, and _<segmentNumber>_<monotonicallyIncrementingCountOfUpdate>.fnm files, we track the Lucene major version available in the respective .dvm/.dvd file's name.

Related Issues

Resolves #7722

Check List

• New functionality includes testing.
  • All tests pass
• New functionality has been documented.
  • New functionality has javadoc added
• Commits are signed per the DCO using --signoff
• Commit changes are listed out in CHANGELOG.md file (See: Changelog)

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 (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/17690/
• CommitID: 72fb904
  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?

[andrross]

Can you add unit tests for the new functionality?

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/17705/
• CommitID: 6431f82
  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 (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/17713/
• CommitID: 3a5dfcc
  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?

[BhumikaSaini-Amazon]

Some integration tests are failing, looking into those

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/20668/
• CommitID: 0e1adb4
  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 (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/20669/
• CommitID: de3324a
  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 (Jenkins) Run Completed with:

• RESULT: UNSTABLE ❕
• TEST FAILURES:

      1 org.opensearch.indices.replication.SegmentReplicationAllocationIT.testSingleIndexShardAllocation

• URL: https://build.ci.opensearch.org/job/gradle-check/20672/
• CommitID: c795f71
  Please review all flaky tests that succeeded after retry and create an issue if one does not already exist to track the flaky failure.

[BhumikaSaini-Amazon]

org.opensearch.indices.replication.SegmentReplicationAllocationIT.testSingleIndexShardAllocation is likely flaky, as per #8279

[opensearch-trigger-bot]

The backport to 2.x failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/backport-2.x
# Create a new branch
git switch --create backport/backport-8088-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 611ecc2ad50c7e1833e7fe8ef2a6cabeb6028c57
# Push it to GitHub
git push --set-upstream origin backport/backport-8088-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/backport-2.x

Then, create a pull request where the base branch is 2.x and the compare/head branch is backport/backport-8088-to-2.x.