Ignore retired and deleted bikes

[benCoomes]

What

closes #60

Why

Delete and retired bikes should never be used in a new ride, so ignore them from consideration.

Details

When updating an activity, get the gear details for each gear we are considering and check that it:

1. Still exists in Strava
2. Is not retired

Ignore any activities that use missing or retired gear when processing events. We do not make a request for more activities if most (or all) of initially requested activities are filtered out.

This also adds an N+1 request to the strava API - we make a single request for each unique gear ID appearing in recent activities. These requests are made concurrently, so impact on duration should is minimized, but it could consume our API limits more quickly.

AFAIK there is no way to request all the gear details for an athlete, or pass a list of gear IDs.

Commits

• remove broken lighthouse action
• add strava api scripts
• add gear model and client
• consolidate strava gear, athelete, activity client
• refactor strava client
• discard activities with retired gear during classification
• Handle gear that no longer exists

[github-actions]

Azure Static Web Apps: Your stage site is ready! Visit it here: https://kind-ocean-0a357fa0f-61.eastus2.azurestaticapps.net