[WFCORE-6755] Move the org.wildfly.security:wildfly-elytron-dynamic-ssl artifact into its own module

[yersan]

Supersedes #5947

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

See https://wildfly.zulipchat.com/#narrow/stream/174184-wildfly-developers/topic/Layers.20and.20optional.20packages.

This PR includes #5947 but removes the community stability property configuration from org.wildfly.security.elytron-dynamic-ssl JBoss Modules module and adds its package as required for the Elytron layer. Until getting a better approach for this case, this will fix the issue reported by the test case where this module was not provisioned when using Elytron Galleon Layer and ensure we can use default stability level out of the box when the server is built targetting this stability level.

[wildfly-ci]

Core -> Full Integration Build 13655 outcome was FAILURE using a merge of 1fc8829
Summary: Tests passed: 169, ignored: 4; exit code 1 (Step: Test full with JDK 11 (Maven)) (new) Build time: 00:17:42

[yersan]

Hello @fjuma / @darranl , a friendly reminder that I requested any of you to review this one, thanks!

[yersan]

@fjuma / @darranl, sorry for the noise, forget my last comment, I have to review the current status first since I lost track of this one, I'm going to remove you from the review until this one gets refreshed

[darranl]

@yersan FYI I will be working on a PR to promote this to default soon, although would be good to know we could solve this situation if it comes up again so I think still worth proceeding for now.

[darranl]

@yersan are we proceeding with this one?

[yersan]

@darranl I want to back to this once we have passed the feature freeze, I plan to take a closer look next week

[yersan]

@darranl kicked it off again, I've added valid-for-stability to the package dependency for Elytron layer, does mean, the package will not be provisioned for an stability level with higher stability than "community"