Eliminate use of separate 'eap' module slot for web content

We use a different module slot for EAP variants of various web content. But with wildfly-to-product that really shouldn't be necessary. The eap-ization commits drop the community content in the 'main' module and then add new content in 'eap' but an option is just to replace in 'main'.

Using a different slot adds complexity, e.g. problems like JBEAP-19748.