Changes

Fixes resource management configuration causing test failure
When disabling the maven-resources-plugin to prevent WildFly from being 
downloaded during test execution in modules that do not need it, the
inclusion of resources in the packages was also disabled.
This led to errors in the execution of tests in other modules that could
not find the XMLs of the datasets or the script files.
This problem has been solved by disabling the “copy-wildfly-resources” 
execution configuration in modules that do not need WildFly instead of 
disabling the “maven-resources-plugin” plugin completely.