cache facet min and max times as ISO8601 in apiKeyAttributes; added an admin api method to do it for all user's at once
Merge branch 'development' of github.com:fluxtream/fluxtream-app into ApiKey-timeBounds
we won't have cached timebounds attributes if the connector is not synchable or doesn't have any facets or is fluxtream_capture
added index on the location source (doh)
-BodytrackResponders now look for ApiKey attributes for min/max time and fallback to facet lookup if that fails
-When connectors/installed is looking up latestData, it was assumed maxTime would be positive (it could be negative in some edge cases so now it just assumes it's more than Long.MIN_VALUE)
Change policy constants in moves updater to space moves update tasks at 30 second intervals when quota is reached and to again go 7 days into the past now that quota handling is improved.
Minor spelling fix in comments
Modified to always call updateTimeBounds when update completes whether or not it is successful and to record the time of the updateTimeBounds call as lastSyncTime rather than the time of the last successful update in the api updates table.
Removed special case for fluxtream_capture when returning lastSync and latestData.  FluxtreamCapture does normal updates, and has photo facets, so it can be treated as a normal connector for this purpose.
Removed fallback methods when asking for latest update and data times.  If the attributes aren't there just return Long.MAX_VALUE.
Merge remote-tracking branch 'upstream/ApiKey-timeBounds' into upstream_development