0.10.0 – backup mode, a fuller backfill, a calm request counter

Backup mode – your Garmin data in your own folder, no Intervals needed – a fuller wellness
backfill, and a request counter that no longer scares anyone.

Added

• Backup mode (BRIDGE_MODE=backup, run --mode backup, or answer 2 in setup):
  your Garmin Connect data in a folder of yours, kept current – no Intervals account needed,
  nothing written anywhere else. Every activity's original FIT with Garmin's summary and
  extras (weather, gear, splits, exercise sets); each day's wellness – the full answers of
  all ~30 endpoints plus the watch's own wellness files (Health Snapshots included) – once
  the day is final and again three days later for a late sync; the account weekly. A run
  every 12 hours (BRIDGE_BACKUP_HOURS), about 60 Garmin requests a day.
  backup --from 2020-01-01 fills in the past, next to a running bridge. Moving to
  Intervals later? The archive is exactly what its modes use. See
  docs/BACKUP.md.

Changed

• A wellness backfill also reads endurance & hill score and race predictions by default
  (15 instead of 12 requests per day; --endpoints essential for the old set) – thanks
  @jetty. For days backfilled before:
  --endpoints endurance_score,hill_score,race_predictions --force-wellness.
• Swap mode's wording says plainly that the deleted copy is the one in Intervals – nothing
  on Garmin Connect is ever touched (thanks @darken).

Fixed

• The daily summary ("last 24 h … Garmin requests" on the web page and in the health log)
  counted far too many Garmin requests when the bridge runs as run: every minute's check
  recorded the whole request count of the last full run again – 50 real requests showed up
  as 2,000. Only the count was wrong, not the requests – thanks @Jeroen_Doesburg.

Install: pip install -U garmin-intervals-bridge (Windows: py -m pip install --upgrade garmin-intervals-bridge), or the image ghcr.io/futureweb/garmin-intervals-bridge:0.10.0 / futurewebat/garmin-intervals-bridge:0.10.0 (Docker Hub).