Remove "JBoss" code from Soteria

[darranl]

This code is based on the PicketBox implementation which is no longer present in WildFly.

[keilw]

@darranl Why should it have to be removed? I assume it has something to do with the "wildfly" build profile?

[keilw]

Is there any relationship to #246?

[darranl]

@keilw Soteria is now Jakarta EE 10, the first WildFly release to be Jakarta EE 10 will be WildFly 27. The "jboss" code presently contained within Soteria is non functional as the various classes referenced by this integration no longer exist.

Regarding #246 this should now be closed as WildFly 15 is no longer a suitable target for testing. The following issue will update to provision WildFly 27 suitable for testing with Soteria #276

For the "jboss" code to be deleted a replacement is needed for WildFly hence #327 to make it easier to plug in server specific implementations, it looks like the initial classes used by SecurityContextImpl were designed as interfaces to make them pluggable but this was never exposed.

[arjantijms]

Thanks @darranl

Ultimately the integration code present within Soteria should be handled in a better way, preferably by something standardised.