Model Server to Entity Server Refactoring

This is a massive PR I realize. I'll be adding notes throughout to help whoever reviews it.

Big changes:
* Models replaced by Entities - naming, classes, etc.
* Entities have all the features that models had, but also support some features of particles (like velocity, gravity, damping, etc)
* ModelItems used to be stored in the element as vectors of ModelItem instances, this has been switched to being heap allocated EntityItem derived class instances, and the tree elements now contain lists of pointers to those heap allocated items. This optimizes our ability to move them around easily when being edited or animated.
* There are now 3 types of entities, more to come, the three types are: Box, Sphere, and Model.
* The old 32bit server assigned IDs have been replaced by server assigned UUIDs - this fixes several collision bugs in the old code.
* All the editing APIs (add, update, delete, getProperties, etc) have been updated to use faster recursion operators and better strategies for minimal traversal of the tree. - This improved large tree performance significantly (up to 20,000x improvement).
* Entities can be accessed by ID through a hash instead of searching the tree... another big performance improvement.
* Delete entity is now a true message/command and no longer uses the goofy "should die" property.
* Some renaming of "node" in trees to be "element" so as to stick with our naming conventions.
* cleaned up some dead code in the voxel system

I don't understand the implementation of this "else if" case:

(1) creatorTokenOnly is created and filled out... but doesn't appear to be used
(2) there is a second call to _entityToElementMap.contains(entityItemID), which was already known to be 'false'.

Also, it appears that each lookup in the map happens twice.  First we figure out if it is there, and then we get its value by entityItemID which is another lookup.  Lookups in a QHash are undoubtedly fast, but it is probably cheaper to use find(), check the iterator, and then extract the value from the iterator.  Not a blocker, but a theoretical performance improvement.