Replace Deployment Processors Javax dependencies with Jakarta module identifiers

A natural choice to exclude a module from deployment would be to use the module name that contains the jar(s) I want to exclude.

However, at this moment and as part of our process to transition to Jakarta EE 10, WildFly deployment processors are still adding the (javax) module alias instead of the target module (jakarta). For example, to exclude jakarta.activation-api-2.1.1.jar I have to exclude javax.activation.api alias instead of jakarta.activation.api

That makes it more difficult to correctly identify which module I need to exclude on my deployment.