VIP Models: Data Structure

[mguidon]

To make the workflow compatible with the current approach in the desktop version, I need the exact same metadata as we get out of the IT'IS server
I addition I need the type of the model which is one of

enum eModelCategory {
        kHumanWhole,
        kHumanRegion,
        kAnimalWhole,
        kCompPhantom,
        keModelCategorySize
    };

Also, this needs to be in synched (at least with the license servers)

[mguidon]

Add the db manually once and add some synchronization for later

[matusdrobuliak66]

Discussed with @odeimaiz DB changes needed:

• Features to proper Object
• add display_name entry: features.name + features.version (+ sorting)
• add category field
• camelCase (not really important)

[pcrespov]

these will be the Identifiers for the categories

These identifiers correspond to the original vip api and are passed to the webserver app in the settings