Fix bwcVersions after bumping version 1.3.1

[nknize]

This version needed to be added after bumping 1.3 branch to 1.3.1 in #2509

[reta]

@nknize we need to add 1.3.1 to Version.java as well:

public static final Version V_1_3_1 = new Version(1030199, org.apache.lucene.util.Version.LUCENE_8_10_1);

[nknize]

@nknize we need to add 1.3.1 to Version.java as well:

public static final Version V_1_3_1 = new Version(1030199, org.apache.lucene.util.Version.LUCENE_8_10_1);

I just saw that! Pushed the constant. thx!

[dblock]

Hopefully by next iteration the auto-increment workflow will kick in and work so we don't need to do this by hand.

[tlfeng]

Not related to this PR, but a thought regarding adding new BWC version in main branch, after adding version in branches of lower versions.
The same negligence occurred just 10 days ago, and fixed by PR #2430. Maybe some documentation needs to be added, and remind people who adding new BWC version in branches other than main.
Update: just saw @dblock comment on above 😄. It's a good solution.

[dblock]

#2430

I think it wouldn't hurt to have a test that runs part of a gradle precommit / check that all these versions are in sync.

[opensearch-ci-bot]

❌   Gradle Check failure 4a14238
Log 3593

Reports 3593

[nknize]

I think it wouldn't hurt to have a test that runs part of a gradle precommit / check that all these versions are in sync.

Sounds like a great first issue or something for the Infra / Build team to pick up!

[dblock]

I think it wouldn't hurt to have a test that runs part of a gradle precommit / check that all these versions are in sync.

Sounds like a great first issue or something for the Infra / Build team to pick up!

#2533

[opensearch-ci-bot]

✅   Gradle Check success 79edaaf
Log 3594

Reports 3594