[WFCORE-7247] [Community] Filtering mechanism for management audit logging and configuration change history

[yersan]

Jira issue: https://issues.redhat.com/browse/WFCORE-7247

WildFly propossal: wildfly/wildfly-proposals#769

[yersan]

Still a draft since I still see some gray areas and want to get some early feedback:

1. I'm not sure if how we are finding the attributes flagged as Redactable in the ModelNode that represents the current operation is correct. We have to find recursively over all the ModelNode paths. See https://github.com/yersan/wildfly-core/blob/a44b627f3b6bc03b806646da7bfb51934bf03061/controller/src/main/java/org/jboss/as/controller/AbstractOperationContext.java#L690-L735

2. Similarly, we need to identify which attributes were flagged with the Redactable flag, but we also have complex attribute definitions that can contain other attribute definitions and that could produce an arbitrary deeph path. See https://github.com/yersan/wildfly-core/blob/a44b627f3b6bc03b806646da7bfb51934bf03061/controller/src/main/java/org/jboss/as/controller/OperationDefinition.java#L120-L153

3. The bump of the management XSD versions, it seems code was only prepared to take into account the schema with the maximun version across all the stability levels, so I was being forced to bump both default xsd to 21 and community xsd to 21, since 21 would be the maximun value. I've changed this so the server can pick up default 20 and community 21. The change here is only on the community XSD so I don't see the point to bump also default, however it looks like the original intention was to always keep them at the same version level, so not sure if my cyurrent approach is correct. See https://github.com/wildfly/wildfly-core/pull/6679/changes#diff-05a1ac6c7737df6cf1405f1edde50f98ecfc25fa72351dded577c4ab4fbe3ec4R104-R119

For 1. and 2., let me ping @jamezp and @bstansberry
For 3. let me ping @darranl

When you have a chance, could you provide some feedback about this? thanks

Notice I've have added only a test for the configuration changes, the one for the autditlog is still in progress. Also, identify the list of attributes that should be flagged as redactable probably will be a collective effort

[yersan]

Rebased, minor tweaks, added more attributes from Elytron subsystem that seems are candidates to be flagged as redactable

[yersan]

Added Audit log test case

[github-actions]

There has been no activity on this PR for 45 days. It will be auto-closed after 90 days.