Fix/2659 deprecation messages updated

[amitchakraborti9]

Description

Some deprecation messages refer to Elasticsearch version 8.0. Now they do not refer to Elasticsearch.

Issues Resolved

Issue #2659

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/4235/
• CommitID: 09f8e87

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: UNSTABLE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/4236/
• CommitID: cab5cb0

[dblock]

I think we want to be specific like before with ES 8.0. We remove deprecations in the next major version, which will be 3.0?

[amitchakraborti9]

Should I reframe the messages from "...is deprecated and will be removed in 8.0." to "...is deprecated and will be removed in 3.0"?

[github-actions]

Gradle Check (Jenkins) Run Completed with:

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

[dblock]

Should I reframe the messages from "...is deprecated and will be removed in 8.0." to "...is deprecated and will be removed in 3.0"?

I think so, yes.

[minalsha]

Hi @amitchakraborti9 , could you please share latest status on this PR and progress? Please reach out if you need any help? Thanks

[amitchakraborti9]

I will be updating the PR today with this change today wherever "is deprecated and will be removed in 8.0" is mentioned.

Should I reframe the messages from "...is deprecated and will be removed in 8.0." to "...is deprecated and will be removed in 3.0"?

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: SUCCESS ✅
• URL: https://build.ci.opensearch.org/job/gradle-check/12412/
• CommitID: 73a2279

[amitchakraborti9]

I have made a new commit on the current version.

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: UNSTABLE ❕
• TEST FAILURES:

      2 org.opensearch.backwards.MixedClusterClientYamlTestSuiteIT.test {p0=indices.shrink/30_copy_settings/Copy settings during shrink index}

• URL: https://build.ci.opensearch.org/job/gradle-check/12413/
• CommitID: d8af97a
  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: UNSTABLE ❕
• TEST FAILURES:

      2 org.opensearch.backwards.MixedClusterClientYamlTestSuiteIT.test {p0=indices.shrink/30_copy_settings/Copy settings during shrink index}

• URL: https://build.ci.opensearch.org/job/gradle-check/12413/
• CommitID: d8af97a
  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-commenter]

Codecov Report

Merging #4719 (d8af97a) into main (73a2279) will decrease coverage by 0.39%.
The diff coverage is n/a.

📣 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    #4719      +/-   ##
============================================
- Coverage     71.22%   70.83%   -0.39%     
+ Complexity    59521    59173     -348     
============================================
  Files          4803     4803              
  Lines        283208   283208              
  Branches      40842    40842              
============================================
- Hits         201712   200623    -1089     
- Misses        65266    66111     +845     
- Partials      16230    16474     +244     

Impacted Files	Coverage Δ
...pensearch/ingest/useragent/UserAgentProcessor.java	63.41% <ø> (ø)
...ensearch/index/mapper/ParametrizedFieldMapper.java	98.59% <ø> (ø)
.../java/org/opensearch/index/mapper/TypeParsers.java	81.39% <ø> (ø)
...h/rest/action/admin/indices/RestResizeHandler.java	67.64% <ø> (ø)
...va/org/opensearch/index/mapper/MapperTestCase.java	95.81% <ø> (ø)
...g/opensearch/test/rest/OpenSearchRestTestCase.java	4.04% <ø> (ø)

... and 464 files with indirect coverage changes

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

[dreamer-89]

LGTM! Thank you @amitchakraborti9 for fixing this.

[dreamer-89]

@dblock : Please have a look. Let know if you have any concerns.

[opensearch-trigger-bot]

The backport to 1.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-1.x 1.x
# Navigate to the new working tree
pushd ../.worktrees/backport-1.x
# Create a new branch
git switch --create backport/backport-4719-to-1.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 16797d658125a8c28ddf49413222f30675352dd6
# Push it to GitHub
git push --set-upstream origin backport/backport-4719-to-1.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/backport-1.x

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

[opensearch-trigger-bot]

The backport to 1.3 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-1.3 1.3
# Navigate to the new working tree
pushd ../.worktrees/backport-1.3
# Create a new branch
git switch --create backport/backport-4719-to-1.3
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 16797d658125a8c28ddf49413222f30675352dd6
# Push it to GitHub
git push --set-upstream origin backport/backport-4719-to-1.3
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/backport-1.3

Then, create a pull request where the base branch is 1.3 and the compare/head branch is backport/backport-4719-to-1.3.