Jakarta EE Platform 12 Milestone 2

Nobody has claimed this yet.

For Milestone 1, if possible it would be ideal to complete the following minimum actions. Milestone 1 work should be completed by October 15 including API, Javadoc, and specification doc artifacts being available. Ideally there would also be a Milestone version of the TCK as well. Status for the Milestone 1 issues will be tracked using [this dashboard](https://github.com/orgs/jakartaee/projects/20/views/1).

**GitHub updates**
- [ ] Service release branch created for N-1 release
- [ ] New / master / main branch up-to-date with service release updates from previous version
- [x] If not done, move from master branch to main.
- platform and platform-tck repos both have main branch

**Code updates**
- [ ] Version update to the new version number including updating Export and Import versions in API jar’s MANIFEST.MF and Specification document
- [x] TCK brought over from platform repo if appropriate (do not delete from platform-tck repo until ratified)
- not applicable
- [ ] Remove all tests from exclude list
- https://github.com/jakartaee/platform-tck/pull/2442 may be the work for this item.
- [ ] Updates for the SEO change in the specification document as outlined in https://github.com/jakartaee/platform/issues/1108
- [x] Do changes necessary to remove references to Java SecurityManager from the spec and API as outlined in https://github.com/jakartaee/platform/issues/1018
- Not applicable. Was done in EE 11.

**CI updates**
- [ ] OSSRH updates
- [ ] TCK running with EE 11 ratifying implementation with Java 21 (tests could be failing due to new tests added / excluded tests no longer removed) and any other LTS versions supported by your new version. Bonus points for Java 25 running.
- [ ] Jenkins job created for the new version for API, Javadoc, spec and TCK
- [ ] Make sure service stream Jenkins jobs are working for API and TCK

Start by reviewing the platform and platform-tck repositories, the linked TCK issue, and the referenced specification issue. Check the remaining milestone checklist items across branches, API and specification artifacts, TCK execution, OSSRH, and Jenkins; done means the applicable items are completed and their status is recorded.

Written by the indexing model from the issue text.