Service Release 3.0.3

[KyleAure]

We should consider creating a service release that includes the following commits for Jakarta EE 10:

• ArrayIndexOutOfBoundsExeption from DST code #275
• Refactoring CronTrigger variable names #327
• Avoid transaction race condition #326

These fixes will go a long way to ensure the Jakarta EE 10 distribution is stable.
Also if anyone has PRs they'd like to see go into a service release now would be the time to add them to the list.

Creating a service release at this point, however, is complicated by the fact that these commits are intermixed with changes for EE 11 which means we will need to cherry pick the changes.

[KyleAure]

I took a look at this and I think we can use the RELEASE-3.0.2 branch to introduce the changes we want for the 3.0.3 release.
The RELEASE branch is meant for development, whereas the TAG 3.0.2 will maintain the state of the repository when 3.0.2 was released.
Then, once the changes are in, we can use Jenkins to stage the service release which will create the RELEASE-3.0.3 branch (for further development) and the 3.0.3 tag.
After verifying the behavior of the service release API/TCK we can then publish the release.

[KyleAure]

It has been two weeks and there has been no objection to creating this service release so I will go forward with creating it. Thank you.

[KyleAure]

Service 3.0.3 has been successfully staged:

• API: https://jakarta.oss.sonatype.org/content/repositories/staging/jakarta/enterprise/concurrent/jakarta.enterprise.concurrent-api/3.0.3/
• TCK: https://jakarta.oss.sonatype.org/content/repositories/staging/jakarta/enterprise/concurrent/jakarta.enterprise.concurrent-tck/3.0.3/

And GitHub has been updated:

• Tag: https://github.com/jakartaee/concurrency/releases/tag/3.0.3
• Branch: https://github.com/jakartaee/concurrency/tree/RELEASE-3.0.3

[KyleAure]

The concurrency service release is now available publicly through sonatype:
Jakarta Repo: https://jakarta.oss.sonatype.org/content/repositories/public/jakarta/enterprise/concurrent/
Maven Central: https://repo1.maven.org/maven2/jakarta/enterprise/concurrent/
(UI typically takes a day to update)