Run publish maven snapshots on all branches matching pattern

[cwperks]

Description

Updates the branches that publish-maven-snapshots github workflow is run with. It now uses a regex to match any released of unreleased branches. I noticed that the .NET client was using the same patterns: https://github.com/opensearch-project/opensearch-net/blob/main/.github/workflows/test-jobs.yml#L16-L17

Related Issues

Resolves #7705

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.

[cwperks]

Does this need a CHANGELOG entry?

[reta]

Does this need a CHANGELOG entry?

I think no, no code changes

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: SUCCESS ✅
• URL: https://build.ci.opensearch.org/job/gradle-check/16117/
• CommitID: 340e754

[codecov]

Codecov Report

Merging #7709 (aaf72e1) into main (b4b3724) will increase coverage by 70.64%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             main    #7709       +/-   ##
===========================================
+ Coverage        0   70.64%   +70.64%     
- Complexity      0    56108    +56108     
===========================================
  Files           0     4680     +4680     
  Lines           0   266081   +266081     
  Branches        0    39067    +39067     
===========================================
+ Hits            0   187983   +187983     
- Misses          0    62155    +62155     
- Partials        0    15943    +15943     

see 4680 files with indirect coverage changes

[cwperks]

@gaiksaya @reta Is there anything outstanding for this PR? It should be good to go.

[reta]

@gaiksaya @reta Is there anything outstanding for this PR? It should be good to go.

Not from me, @gaiksaya LGTM?

[gaiksaya]

Hey! So we won't be releasing anything before 1.3 so not sure if that regex should cover only 1.3 and 2.7.x
Basically since 2.7 is out nothing before that in 2.x series ever be released following semver. Do we still want to keep publishing to those versions?
Basically all we want is:

main
1.3
2.x
2.7 <--------- whatever automation creates version increment PRs modify it to bump this to 2.8 once 2.8 is released

Sample PR: #7371
@andrross @dblock Would like your input here.

[dblock]

@gaiksaya Are you saying hard-code that list? That seems alright by me. That list would be true for more than a year.

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/16539/
• CommitID: 1ff15f0
  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 (Jenkins) Run Completed with:

• RESULT: UNSTABLE ❕
• TEST FAILURES:

      1 org.opensearch.backwards.MixedClusterClientYamlTestSuiteIT.test {p0=tasks.list/10_basic/tasks_list test}

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

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: UNSTABLE ❕
• TEST FAILURES:

      1 org.opensearch.cluster.allocation.ClusterRerouteIT.testDelayWithALargeAmountOfShards
      1 org.opensearch.backwards.MixedClusterClientYamlTestSuiteIT.test {p0=tasks.list/10_basic/tasks_list test}

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

[gaiksaya]

@gaiksaya Are you saying hard-code that list? That seems alright by me. That list would be true for more than a year.

Yeah it is hard coded but branches like 2.7, 2.8 needs to be updated regularly so was recommending the version increment automation to accommodate this change as well. Looks like the current approach with regex works as well?

[gaiksaya]

Adding above labels to backport to 2.x, 2.8 and 1.3 branches for now.
Thanks!