store track details

Nobody has claimed this yet.

`detail["frequencyList"]` is a list of

```
{'altitude': 77,
'cadence': 164,
'cadenceLength': 101,
'distance': 2800,
'gpsLat': 447678130,
'gpsLon': -1230242061,
'heart': 102,
'heartLevel': 1,
'power': 135,
'slope': 0,
'speed': 360,
'timestamp': 164497134500}
```

I think it's approximately one per second (?).

I'd like to store this in a way that makes sense. A polyline via Spatialite makes a lot of sense -- that would let me draw maps etc -- but the last time I did this I recall that storing the extra info (HR, power, etc) alongside that spatial data is weird. A separate table with one row per point would work too, I guess, but be pretty unweildly.

There's also #4 for the raw file, which is a different way of getting this same data. Some redundancy here is OK too I think.

No file or test is named. Start by tracing how detail["frequencyList"] is currently read and compare the raw-file path in issue #4. Done means choosing and implementing a storage model that preserves the track points and fields such as cadence, heart rate, power, GPS coordinates, and timestamps.

Written by the indexing model from the issue text.