chore: remove unused/broken BlueBikes widget

[digitalcora]

This feature has been unused since the original Orange Line "surge" it was developed for in mid-2022, and non-working since July 2023, when the data fetching was commented out due to persistent crashes (see 9211202).

We should avoid leaving code committed that will never be executed and/or features available in the admin UI that don't work. Should we choose to prioritize this feature again, the old code lives on in the history of the repo for reference.

[robbie-sundstrom]

Everything that's deleted here makes sense!

Looking through the code for anything else related to clean up, I found one a reference to a bike_issue for alerts. I don't believe that's related, but also haven't been able to figure out what it's actually for. Do you know if that's needed?

[digitalcora]

bike_issue is a possible effect type for alerts (alerts have "effect" and "cause" enums which are sort of like "what's happening" and "why is it happening" respectively). For completeness we have all the known cause/effect types in our alert parsing even if we don't do anything specific with them. So this is all unrelated to BlueBikes service — an alert with an effect of bike_issue might be used if an MBTA-owned bike cage at a station was inaccessible, for example.

[robbie-sundstrom]

gotcha, having all alert types, even ones we don't use explains it! I see other alert types that aren't used either now

[robbie-sundstrom]

Cleaning up old code like the hero our team needs 🦸‍♀️