Draft: Forward Attributes from WildFly Elytron SecurityIdentity to the Builder for Quarkus SecurityIdentity

[MelkorCC]

Draft fix for #44804

[sberyozkin]

Hi @MelkorCC, thanks, can you tell me please, for example, in this integration test, https://github.com/quarkusio/quarkus/tree/main/integration-tests/elytron-security-jdbc/src/main/resources, what can I set, either in properties, or the SQL script, to test that the extra attributes have been propagated ?

[MelkorCC]

@sberyozkin hi, in my commits you can see what i did tried for ldap (that is why i left them there for now, we should of course ultimately squash them).

The main changes on the config side for the ldap integration test would be the attribute mapping in the properties and of course providing the attribute in the ldif .

[sberyozkin]

Thanks @MelkorCC, I've opened another PR #44896 to make it easier to deal with merge commit issues, thanks for your contribution 👍