[WFLY-15978] Enable Elytron security domains for all connectors

[bstansberry]

Issue: https://issues.redhat.com/browse/WFLY-15978
Upstream: #15157

[bstansberry]

@tadamski @reinhapa I ported this to the 26.x branch for possible inclusion in WF 26.1.

[darranl]

I am going to close for now as the upstream fix is being reviewed, we can either reopen or create a new backport if we think the resulting changes could be included in WildFly 26.1.1

[reinhapa]

@darranl sad, so I will have to patch it in this case...

[tadamski]

@reinhapa I'm working on alternative PR

[reinhapa]

@tadamski any chance to have this in a later 26.1.1?

[tadamski]

hi @reinhapa
I have opened PRs which move Elytron configuration metadata to IronJacamar code:
ironjacamar/ironjacamar#750
#15440
The idea behind those is that you can mark IJ resources as Elytron enabled by adding 'elytron' tag in the configuration. This way such configurations can work with new WildFly/EAP and be verified as Elytron based. OTOH we are avoiding transforming all legacy configs to Elytron under the hood (possibly without the knowledge of the deployment creator).

[reinhapa]

I have opened PRs which move Elytron configuration metadata to IronJacamar code:
@tadamski I saw that you're PR ironjacamar/ironjacamar#750 has been closed. Did it not make it into the IronJacamar code base? Does this mean, that my change has been rolled back and no alternative is available for now?

[tadamski]

hi @reinhapa
I have reopend those PR as draft ones:
ironjacamar/ironjacamar#754
#15556