[Upgrade] Lucene 9.5.0 release

[nknize]

Upgrades to official release of Lucene 9.5.

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/10183/
• CommitID: 89f64e9
  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/10182/
• CommitID: 5852bd9
  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]

Swapped around the labels because I assume this will go into the 2.6 release. @nknize please correct me if I'm wrong.

There does seem to be a related test failure though:

REPRODUCE WITH: ./gradlew ':modules:analysis-common:test' --tests "org.opensearch.analysis.common.HighlighterWithAnalyzersTests.testPhrasePrefix" -Dtests.seed=68DBA7498B3491B9 -Dtests.security.manager=true -Dtests.jvm.argline="-XX:TieredStopAtLevel=1 -XX:ReservedCodeCacheSize=64m" -Dtests.locale=en -Dtests.timezone=Pacific/Auckland -Druntime.java=19

org.opensearch.analysis.common.HighlighterWithAnalyzersTests > testPhrasePrefix FAILED
    java.lang.AssertionError: 
    Expected: map containing ["field0"->ANYTHING]
         but: map was []
        at __randomizedtesting.SeedInfo.seed([68DBA7498B3491B9:183142C700C72FBE]:0)
        at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:18)
        at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:6)
        at org.opensearch.test.hamcrest.OpenSearchAssertions.assertHighlight(OpenSearchAssertions.java:430)
        at org.opensearch.test.hamcrest.OpenSearchAssertions.assertHighlight(OpenSearchAssertions.java:420)
        at org.opensearch.test.hamcrest.OpenSearchAssertions.assertHighlight(OpenSearchAssertions.java:399)
        at org.opensearch.analysis.common.HighlighterWithAnalyzersTests.testPhrasePrefix(HighlighterWithAnalyzersTests.java:283)

[nknize]

Swapped around the labels because I assume this will go into the 2.6 release. @nknize please correct me if I'm wrong.
👍🏻

There does seem to be a related test failure though

Fixed up MultiPhrasePrefixQuery based on some QueryVisitor and highlighter changes; should be passing now...

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: null ❌
• URL: null
• CommitID: 856560e
  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: null ❌
• URL: null
• CommitID: 856560e
  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: ABORTED ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/10266/
• CommitID: 856560e
  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: SUCCESS ✅
• URL: https://build.ci.opensearch.org/job/gradle-check/10314/
• CommitID: 856560e

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: UNSTABLE ❕
• TEST FAILURES:

      1 org.opensearch.indices.replication.SegmentReplicationRelocationIT.testPrimaryRelocationWithSegRepFailure

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

[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-6078-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 8d5d2e6b10db66784279c72715fb643f0fed38d0
# Push it to GitHub
git push --set-upstream origin backport/backport-6078-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-6078-to-2.x.