The previous Maven configuration included a WildFly Maven plugin
configuration in the H2 and MySQL profiles that allowed the application
execution directly from Maven (with the mvn wildfly:start wildfly:deploy
command). As this configuration included a custom WildFly deployment
configuration (that modified the standalone.xml of the WildFly where the
application will be deployed), the mvn wildfly:deploy couldn't be used
to deploy the application in a local WildFly instance.

This commit adds a new profile (wildfly-mysql-run) that can be used to
execute the application directly from Maven (with the mvn install
command). The custom WildFly plugin configuration has been removed from
the other profiles, allowing users to normally deploy the application in
a running WildFly instances.

Instructions on how to use the profiles for application execution and
deployment can be found in the README.md file.

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.

The IsEqualToEntity matcher (previously, IsEqualsToEntity) has been
improved to allow property comparison by functional reference to the
getter methods of the properties to compare. Specifically, the
"checkAttribute" methods added allow providing a Function<T, R> as a
getter, where T is the type of the entity to compare and R is the type
returned by the getter method.

Some test of the service and rest projects have been updated for better
coverage, achieving a 100% coverage in most of them.

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.

Missing version for compiler, javadoc, source and deploy plugin in POM was
causing some warning messages during the compilation with Maven.

In addition, the Javadoc was fixed in the OwnerService and PetService
classes.

The addition of the jboss-ejb3.xml file with the security domain
configuration allows the deployment of the "services" project as an
independent project in a Wildfly/JBoss container.

Some test classes have been refactorized for a more consistent use of
the OwnersDataset class and for a simpler test implementation.

The REST layer has been added but with incomplete tests. Students will
have to complete the tests.

This commit includes an important refactorization regarding tests. Test
classes and datasets have been moved from the "service" project to a new
"tests" project. This way, any project can include this "tests" project
as a dependency in order to have access to these common testing
resources.

This commit adds the OwnerService and PetService EJBs to the
implementation. This commit also includes the tests for this EJBs with
two different Wildfly profiles: a H2 profile and a MySQL profile.

The "administrator" entity has been added to represent the
administrators of the application.