Disable BWC tests until they are supported by the distribution

[peternied]

Description

Disable BWC tests until they are supported by the distribution

Issues Resolved

• New issue to track this being fixed Reenable BWC tests once they are operational in our CI checks #2109
• Related [BWC] How should Backwards Compatiabilty tests be configured as we approach v3.0? opensearch-plugins#167
• See also [BUG] org.opensearch.cluster.coordination.CoordinationStateRejectedException upgrading 2.0.1 to 3.0 OpenSearch#3615

Check List

• New functionality includes testing
• New functionality has been documented
• Commits are signed per the DCO using --signoff

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.

[codecov-commenter]

Codecov Report

Merging #2108 (b82bd8a) into main (1fc02ad) will increase coverage by 0.02%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##               main    #2108      +/-   ##
============================================
+ Coverage     60.97%   60.99%   +0.02%     
- Complexity     3226     3227       +1     
============================================
  Files           256      256              
  Lines         18073    18073              
  Branches       3224     3224              
============================================
+ Hits          11020    11024       +4     
+ Misses         5475     5473       -2     
+ Partials       1578     1576       -2     

Impacted Files	Coverage Δ
...a/org/opensearch/security/tools/SecurityAdmin.java	35.75% <0.00%> (-0.25%)	⬇️
...earch/security/ssl/util/SSLConnectionTestUtil.java	95.45% <0.00%> (+2.27%)	⬆️
...urity/ssl/transport/SecuritySSLNettyTransport.java	66.66% <0.00%> (+4.30%)	⬆️

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

[cliu123]

Assuming BWC test is being disabled temporarily, would it be better to just merge PRs that only have the known BWC test failures for now? Otherwise, we wouldn't know if new changes introduce new BWC test failures or only failed because of the known failures.
And we'd also need another PR to enable BWC later when 3.0 supports it. Keeping it running, we'd be able to know immediately when it gets fixed. WDYT? @opensearch-project/security

[peternied]

We have been unable to move to v3.0 for months, and I don't foresee a quick resolution. The aim of this change is to start making incremental progress.

The follow up issues that were created capture reenabling the tests and getting guidance for how to reenable BWC tests (see description for links).

@cliu123 what would you recommend if we don't take this change?

[peternied]

Good news! 2.4.0 is backwards compatible with 3.0.0, I am closing this PR in deference to #2112 that will rev main to 3.0.0