Release copy that supports jakarta

[hazendaz]

Today this code base is on javax. In order to support the future, cut secondary copy that releases as jakarta based.

[adam-waldenberg]

👍 For this one. Just noticed I get a Caused by: java.lang.ClassNotFoundException: javax.annotation.Resource when using @Tests. I guess this can be done with a classifier in other to support both variants.

[hazendaz]

When I checked this last, it was extensive here. So I don't think I want to add a classifier like I've seen on projects like Deltapspike that completely corrupted the dependency resolution doing that. Instead, I'm likely to split the repo formally and support both at separate revision levels. I'll likely call jakarta 2.0.0 (going semantic) and start to officially deviate entirely from keeping 1.49.x to aling with original author. At this point, I've saturated this on 100s of repos and have no desire to go back. So for the legacy javax, will likely start 1.50, 1.51, etc non sematic like was originally and/or may drop .0 on end to give that appearance. What I won't be doing is deleting stuff every other release that was massive issue with the original.