Go for "1.0"

* Set API version to 1.0 (THIS CHANGES ENDPOINTS!)
* do not store position history into database
* clean up position data after config period (default for 5 days)
I'll admit that i was on the fence about this one. It really is a "Swing the cat three times counter clockwise while cutting the bird with the obsidian knife" sort of SQL to remove all but the latest records. I'm a bit attached to it because it was a bugger to come up with, and if we ever decide to add server side tracking history back in, it would be hugely useful rather than dig through the history to find. Obviously, if I restructure the data to remove the position table entirely, then this doesn't matter at all and I can comfortably drop it.