The configuration to execute WildFly using Maven commands was causing
problems in Windows environments.

This problem has been fixed by upgrading the plugin version, which
implied rebuilding its configuration. As part of this change, the
configuration was also simplified, and now starting the application and
redeploying it is faster.

In addition, submodules that do not require WildFly to run the tests
no longer copy it. This reduces the execution time.

The project configuration has been simplified by unifying some part of
the mysql and h2 configurations.

In addition, the project has been configured to allow the execution of
the application with the Maven WildFly plugin.

On previous commits, the name of the EAR was changed but the Wildfly plugin
wasn't updated to use the new name. This commit changes the Wildfly deployment
configuration to fix this problem.

The README.md has been update to reference the new course and the new
Eclipse version. In addition, the general pom.xml file has been updated
to include the newer versions of the dependencies, and the ear/pom.xml
has been modified to include more project information in the generated
EAR.

On the other hand, the testing mysql-ds.xml have been removed and the
standalone.xml testing files have been updated to include the datasource
data.

The JSF and REST modules are now served from the /xcs-sample path.

The JaCoCo plugin has been added to perform the coverage test, while the
Wildfly plugins allows the automatic deployment of the project on a
Wildfly server using the 10990 port as the administration port.

This commit adds the JSF project with a web application that allows the
management of owners (by the administrators) and pets (by the owners).
The JSF project includes the functional tests for the owners management
page.

The EAR project only contains a POM that creates an EAR distribution of
the system.