[Extensions] Add support for minimum compatible version for extensions with OpenSearch

[saratvemulapalli]

Signed-off-by: Sarat Vemulapalli vemulapallisarat@gmail.com

Description

Part of opensearch-project/opensearch-sdk-java#346.
Added support to define minimum compatible version for extensions talking to OpenSearch.
As we are limiting to minor version compatibility for now, we will revisit this validation when major version compatibility is in the works.
Also, cleaning up unnecessary config needed for extensions as most of it is inherited from plugins back in the day.

Issues Resolved

Closes opensearch-project/opensearch-sdk-java#65

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/9869/
• CommitID: 66e4c14
  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/9870/
• CommitID: 07f8c50
  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/9871/
• CommitID: fb2da3d
  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/9872/
• CommitID: 3a658d6

[codecov-commenter]

Codecov Report

Merging #6003 (c899c1a) into main (ebb5813) will decrease coverage by 0.09%.
The diff coverage is 86.95%.

❗ Current head c899c1a differs from pull request most recent head c081cdd. Consider uploading reports for the commit c081cdd to get more accurate results

📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more

@@             Coverage Diff              @@
##               main    #6003      +/-   ##
============================================
- Coverage     70.75%   70.67%   -0.09%     
+ Complexity    58721    58689      -32     
============================================
  Files          4774     4774              
  Lines        280903   280876      -27     
  Branches      40582    40582              
============================================
- Hits         198760   198513     -247     
- Misses        65831    66058     +227     
+ Partials      16312    16305       -7     

Impacted Files	Coverage Δ
server/src/main/java/org/opensearch/node/Node.java	83.13% <50.00%> (-0.10%)	⬇️
.../org/opensearch/extensions/ExtensionsSettings.java	42.30% <66.66%> (+0.74%)	⬆️
.../opensearch/extensions/DiscoveryExtensionNode.java	78.12% <100.00%> (+4.05%)	⬆️
...a/org/opensearch/extensions/ExtensionsManager.java	46.06% <100.00%> (-1.40%)	⬇️
...main/java/org/opensearch/node/NodeMocksPlugin.java	0.00% <0.00%> (-100.00%)	⬇️
...adonly/AddIndexBlockClusterStateUpdateRequest.java	0.00% <0.00%> (-75.00%)	⬇️
...ava/org/opensearch/action/NoSuchNodeException.java	0.00% <0.00%> (-50.00%)	⬇️
...a/org/opensearch/tasks/TaskCancelledException.java	50.00% <0.00%> (-50.00%)	⬇️
.../org/opensearch/client/indices/AnalyzeRequest.java	31.00% <0.00%> (-45.00%)	⬇️
...readonly/TransportVerifyShardIndexBlockAction.java	9.75% <0.00%> (-41.47%)	⬇️
... and 491 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: UNSTABLE ❕
• TEST FAILURES:

      1 org.opensearch.cluster.routing.allocation.decider.DiskThresholdDeciderIT.testIndexCreateBlockWithAReadOnlyBlock
      1 org.opensearch.cluster.routing.allocation.decider.DiskThresholdDeciderIT.testIndexCreateBlockWhenAllNodesExceededHighWatermark

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

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: SUCCESS ✅
• URL: https://build.ci.opensearch.org/job/gradle-check/10093/
• CommitID: c899c1a

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/10096/
• CommitID: c081cdd
  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/10333/
• CommitID: 9b77d0d
  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/10334/
• CommitID: 92e0b4d
  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/10337/
• CommitID: 5ebc8ea
  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/10338/
• CommitID: b13b194
  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/10339/
• CommitID: 4d21452
  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/10340/
• CommitID: da30c35

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

[dblock]

Is this backwards? Why should the server care about the minimum version of a client? I think the extension should be required to provide a declaration for version compatibility and the server should check it.