Update version to 2.18.0 for CatShards request and response

[gargharsh3134]

Description

Updating version to 2.18.0 for CatShardsRequest and CatShardsResponse which were added as 3.0.0 as part of #14641

Related Issues

Resolves #[Issue number to be closed when this PR is merged]

Check List

• Functionality includes testing.
• API changes companion pull request created, if applicable.
• Public documentation issue/PR created, if applicable.

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 result for 6e4ab14: FAILURE

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 result for fd2f9c0: FAILURE

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]

❌ Gradle check result for fd2f9c0: FAILURE

I suspect the failure in CatShardsRequestTests.testSerializationWithOlderVersionsParametersNotSerialized is related to this change. @gargharsh3134 can you take a look?

[github-actions]

❌ Gradle check result for 2806587: FAILURE

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 result for 9f75286: FAILURE

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 result for c314d98: FAILURE

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 result for c314d98: FAILURE

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 result for 87d7231: SUCCESS

[codecov]

Codecov Report

Attention: Patch coverage is 50.00000% with 2 lines in your changes missing coverage. Please review.

Project coverage is 72.10%. Comparing base (9489a21) to head (87d7231).
Report is 36 commits behind head on main.

Files with missing lines	Patch %	Lines
...action/admin/cluster/shards/CatShardsResponse.java	0.00%	0 Missing and 2 partials ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##               main   #16455      +/-   ##
============================================
+ Coverage     72.04%   72.10%   +0.06%     
- Complexity    65020    65060      +40     
============================================
  Files          5313     5313              
  Lines        303356   303356              
  Branches      43900    43900              
============================================
+ Hits         218551   218742     +191     
+ Misses        66905    66684     -221     
- Partials      17900    17930      +30     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[gargharsh3134]

@dbwiddis @andrross @owaiskazi19 Finally got the build working, had to re-run multiple times owing to flaky tests. Please check whenever you get a chance.
Thanks!

[dbwiddis]

@dbwiddis @andrross @owaiskazi19 Finally got the build working, had to re-run multiple times owing to flaky tests. Please check whenever you get a chance. Thanks!

Winter is coming. (Snow) flakiness is a fact of the season ;)

[dbwiddis]

@gargharsh3134 does this need a 2.x backport?

[gargharsh3134]

@dbwiddis It was already handled while merging the 2.x backport of source PR (#16396). We should be good now.
Thanks!

[dbwiddis]

It was already handled while merging the 2.x backport of source PR (#16396). We should be good now. Thanks!

@gargharsh3134 seems one of these was missed. I manually filed #16590 for 2.18 branch. I'll trigger the backport from this PR to hopefully fix 2.x as the other changes should be no-op.