[Snapshot Interop] Keep API parameters behind remote store experiment…

[harishbhakuni]

…al feature flag.

Description

Documentation Changes for Snapshot Interop Project are still not merged.
We will be launching Snapshot Interop Feature with Remote Store Feature, so as part of this PR we are keeping all the Snapshot Interop related API parameters behind the Remote Store Feature Flag.

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/19709/
• CommitID: 0a19e83
  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?

[gbbafna]

Do we really need these changes ? It might be okay showing some extra flags in API output as it wouldn't break the clients.

[github-actions]

Gradle Check (Jenkins) Run Completed with:

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

[sohami]

LGTM. Let's create a tracking doc change for the new flag in create snapshot response.

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/19802/
• CommitID: 971b559
  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/19809/
• CommitID: 75f1dd3
  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/19810/
• CommitID: 84f86bb
  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?

[gbbafna]

org.opensearch.index.shard.RemoteStoreRefreshListenerTests.testRefreshAfterCommit
org.opensearch.index.shard.RemoteStoreRefreshListenerTests.classMethod
org.opensearch.index.shard.RemoteStoreRefreshListenerTests.classMethod
org.opensearch.index.shard.RemoteStoreRefreshListenerTests.testAfterMultipleCommits
org.opensearch.index.shard.RemoteStoreRefreshListenerTests.classMethod
org.opensearch.index.shard.RemoteStoreRefreshListenerTests.classMethod
org.opensearch.index.shard.RemoteStoreRefreshListenerTests.testAfterMultipleCommits
org.opensearch.index.shard.RemoteStoreRefreshListenerTests.classMethod
org.opensearch.index.shard.RemoteStoreRefreshListenerTests.classMethod
org.opensearch.index.shard.RemoteStoreRefreshListenerTests.testAfterMultipleCommits

Failing tests are not related to this change and are flaky . Merging it as it is important to block interop related params when remote store is not enabled .