Separate data classes from object model

[leonhard-s]

Currently, the "active" classes (e.g. Character, Outfit) are tightly associated with their respective data class (CharacterData and OutfitData respectively).

This seemed like a promising idea initially, but it is already starting to break down with relational data types, which will only worsen as generic sub-query interfaces (#15) or reports (#18) are implemented. There simply are many types of server responses that do not match a collection.

It seems like moving all of these data classes into a separate models module would be a good solution to underline this difference, and it would greatly declutter some of the wordier modules like ps2.fire as well.

[leonhard-s]

A tentative version of the split has been added as of 065a0e9 of the models branch.

This change has led to several tiny modules (i.e. ones with only one or two classes in them), these will be consolidated in an upcoming commit.

[leonhard-s]

The commit mentioned above has just been finalised and pushed to models. Remaining work is tied into other issues and tests (#24), closing this issue as its primary goal was met.