Adding BWC version 1.3.11 to 2.x

[kartg]

Description

In #7629, the 1.3 branch was updated to v1.3.11 automatically. This appears to have broken our BWC builds:

• [Backport 2.x] [Manual Backport] Bump org.jruby.joni:joni from 2.1.48 to 2.2.1 in /libs/grok (#8015) #8051
• [Backport 2.x] Bump com.google.guava:guava from 32.0.0-jre to 32.0.1-jre in /distribution/tools/plugin-cli #8049
• [Backport 2.x] [Manual backport] Bump com.google.guava:guava from 32.0.0-jre to 32.0.1-jre in /distribution/tools/upgrade-cli (#8011) #8054

This problem has cropped up before - #6732

Adding the 1.3.11 version to our list of BWC versions should fix this.

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.

[reta]

@kartg already there #8061

[kartg]

Beat me to it! 😄 thanks @reta !

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: UNSTABLE ❕
• TEST FAILURES:

      1 org.opensearch.cluster.allocation.AwarenessAllocationIT.testThreeZoneOneReplicaWithForceZoneValueAndLoadAwareness

• URL: https://build.ci.opensearch.org/job/gradle-check/17571/
• CommitID: d3313e4
  Please review all flaky tests that succeeded after retry and create an issue if one does not already exist to track the flaky failure.