bug: FIT files have inaccurate distance and speed data

[frenata]

timestamp(s)
heart rate(bpm)	cadence(rpm)	distance(m)	power(watts)	resistance	enhanced speed(m/s)
03/09/202601:30:49 PM	93	76	-	123	20	2.598
01:30:50 PM	93	73	0.06	143	20	2.622
01:30:51 PM	93	71	0.06	148	20	2.663
01:30:52 PM	93	70	0.06	183	20	2.792
01:30:53 PM	94	71	0.05	164	20	2.836
01:30:54 PM	96	72	0.07	188	20	2.894
01:30:55 PM	97	73	0.06	156	20	2.799
01:30:55 PM	99	73	0.05	146	20	2.751
01:30:56 PM	101	73	0.07	135	20	2.696
01:30:57 PM	104	73	0.07	139	20	2.641

[frenata]

#52 did not fix this

it looks like different FIT parsers are handling this differently now:

• intervals.icu now recognizes a short 1km ride as really 1km ride over ~2 minutes with a mostly steady state of ~30 kph
• strava shows it as 0.3 km with sporadic speeds of 5-15 kph
• fitfileviewer shows (as it has on previous recordings) two sessions -- one that has the right distance but lasts less than a second, and another that has no distance but lasts ~2 minutes

Presumably the last issue points the way forward (timestamp mismatches?) or #24 does.