Remove SecurityManager
Do we know that all downstream consumers (specifically WildFly) are OK with not having security manager support?
WildFly is going to need to retain security manager support as long as we are supporting Jakarta EE 10 - this also looks to be submitted to a branch which is producing micro releases, should a removal like this trigger a larger version bump?
We only set the release version on the actual release. Right now, it is just the version generated by Maven. We may consider moving to something like 999-SNAPSHOT for development like Quarkus.
Ok, let's keep the SecurityManager for a little longer.