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.
interesting. It seems like maybe a better fix would be to do this inside of EntityItemProperties. Basically when the properties "object" gets constructed... the created time and last edited times are unknown. If you set the created time... it seems like it should also force a last edited time to match the created time. I can't see why you'd ever have something with a created time greater than the last edited time... creation is by definition editing...