RFC: Save PetData and RiderPetData as a bitmask. Fixes #107

**DO NOT MERGE YET**. This contains changes to the EchoPet table structure without proper migration.

This change fixes #107, and changes the table structure to:

```
+--------------+--------------+------+-----+---------+-------+
| Field        | Type         | Null | Key | Default | Extra |
+--------------+--------------+------+-----+---------+-------+
| OwnerName    | varchar(255) | NO   | PRI |         |       |
| PetType      | varchar(255) | YES  |     | NULL    |       |
| PetName      | varchar(255) | YES  |     | NULL    |       |
| PetData      | int(11)      | YES  |     | NULL    |       |
| RiderPetType | varchar(255) | YES  |     | NULL    |       |
| RiderPetName | varchar(255) | YES  |     | NULL    |       |
| RiderPetData | int(11)      | YES  |     | NULL    |       |
+--------------+--------------+------+-----+---------+-------+
```

.. where PetData and RiderPetData are bitmask serializations as defined in [SQLUtil](https://github.com/eueln/EchoPet/blob/b46243075154184d3a7250286b3d883cd4f9e963/modules/API/src/main/java/com/dsh105/echopet/compat/api/util/SQLUtil.java#L27)

Looking for suggestions if you have any.