[TaskCancellationMonitoringService] Changing version check to 2.9

[sgup432]

Description

Changing version check to 2.9.
Related backport PR - #8046

Related Issues

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

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/17600/
• CommitID: 26ea426
  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?

[msfroh]

I hope that we can get this one merged soon, since the version check mismatch is causing BwC test failures on main.

I'm wondering if we could establish a process where we have both PRs for a version check change (on 2.x and main) ready, and the maintainer who merges the 2.x PR commits to merging the main PR immediately after.

I've had a couple of these where I've had a backport PR (that changes a version check to whatever the next 2.x release will be) and associated update in main. I manage to get the backport PR merged, but haven't been able to get the main PR merged until a day later -- after I've annoyed everyone else by breaking their Gradle checks.

I would love a technical solution that doesn't rely on good intentions, but asking the human maintainers to merge both PRs in quick succession is the best I've been able to think of.

I'm going to copy this comment into a dedicated issue. Maybe someone else has a cleverer solution.

[sgup432]

@dblock @andrross @Bukhtawar Can you please help in merging this? As it is causing problems to others as mentioned by @msfroh.

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: UNSTABLE ❕
• TEST FAILURES:

      1 org.opensearch.search.backpressure.SearchBackpressureIT.testSearchTaskCancellationWithHighCpu
      1 org.opensearch.action.admin.cluster.node.tasks.ResourceAwareTasksTests.testBasicTaskResourceTracking

• URL: https://build.ci.opensearch.org/job/gradle-check/17624/
• CommitID: 26ea426
  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]

Codecov Report

Merging #8069 (26ea426) into main (cc0f344) will decrease coverage by 0.03%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##               main    #8069      +/-   ##
============================================
- Coverage     70.98%   70.96%   -0.03%     
+ Complexity    56691    56652      -39     
============================================
  Files          4722     4722              
  Lines        267576   267576              
  Branches      39213    39213              
============================================
- Hits         189950   189876      -74     
- Misses        61646    61657      +11     
- Partials      15980    16043      +63     

Impacted Files	Coverage Δ
...rch/action/admin/cluster/node/stats/NodeStats.java	51.44% <0.00%> (ø)

... and 438 files with indirect coverage changes