more correct creation and edit times for entities

Fixing some bugs that I introduced when I split out EntityItem::_lastSimulated time from EntityItem::_lastUpdated and EntityItem::_lastEdited.

The bugs were not noticeable under normal conditions, but became noticeable when trying to get results from one physics simulation (bullet) to be relayed across the EntityServer and into another interface instance that was running a simpler simulation.  The update packets from the EntityServer were getting rejected at the receiving end because the accompanying _lastEdited time was too old.
same issue I mentioned above... does this change properly support an entity that starts in the air, with gravity, but no velocity? I think it does not correctly determine that that entity should be moved, and therefore it will just be suspended in space.