The list of existing people in a pet owner field has been added to better identify the person we want to select.
In addition, it has been added that in the view of a person's pets, the name of that person appears by default in the form of adding / editing the information of a pet.

Now there are no columns with repetitive information

When the frontend tries to delte a person and the request fails a message is shown to notify the user.

Now the name and surname of the person who owns the pet is displayed instead of its id.
To do this, we have included the getPeople method in the people dao to obtain the information of a specific person and thus obtain the name and surname to be shown in the table.

The files that contain the information to handle the integration tests have been created.

For this, the PetsDataset class has been created in order to have test data and verify the correct functioning of the DAO.
In addition, a matcher has been added to compare pets.

- The authentication header has been added to the test of modifying a person's name.
- Updated the name of the PetDAO class to PetsDAO in the Pets resource.

- It has been added to restart the form after deleting a row.
- Permits have been introduced to the rest resources

When the frontend tries to recover people list and the request fails a message is shown to notify the user.

The PeopleResourceTests now include security tests to verify that normal
users can't access people data.

Changed the attribute breed by specie.
In addition, there are changes in the script that has the lines to build the DB.

- Created the pet table
- Created the pet class