Add support for running the Security 3.0.2 TCK

[scottmarlow]

https://issues.redhat.com/browse/WFLY-19513 is the WildFly tracker for being able to run against the Security 3.0.2 TCK which should soon be promoted for the TCK challenge jakartaee/security#297 (promotion will be coordinated via jakartaee/specifications#764).

It seems that we either have to use the default (Tomcat) OpenID Connect Server being started in a few tests or provide our own OpenID impl for the two tests mentioned in jakartaee/security#297 (comment)

Currently, I see two different side effects of Tomcat being started by the Security 3.0.2 TCK tests. https://gist.github.com/scottmarlow/50802d6a60ca5228fa92d207b4d44a78 shows some unexpected (by me) test output from tomcat in the TCK testing in the form of a Tomcat stack trace and after that for a different test, we see Address already in use /127.0.0.1:8443 error which likely happens due to Tomcat still being in memory.

[scottmarlow]

I'm not sure if we should use the Apache Tomcat OpenID Connect Server or something like https://wildfly-security.github.io/wildfly-elytron/blog/securing-wildfly-apps-openid-connect/

[jamezp]

Do we have a choice? Everything is pretty hard-coded in the TCK and it might be rather difficult to replace it.