fix: Don't show trip-specific alerts in the stop page predictions pane

[joshlarson]

Scope

Asana Ticket: ❗ [AM Alerts] Don't show train(s) specific alerts in stop page predictions pane

Implementation

• Add a utility function to tell whether an alert isTripSpecific.
• Update isDeparturesAndMapAlert to check both the alert effect and to check that an alert is not trip-specific.

Screenshots

Also worth noting: When an alert is not trip-specific, then it will still be included in the predictions pane:

How to test

(If you're testing right now, 2:17PM on Wednesday Jan 28, then there are some helpful test alerts available - the ones pictured above. If you're testing at a different time, you may need to create test alerts that have the effects and specificities you're looking for)

Create a station bypass affecting one train on (for example) the Fall River/New Bedford line at (for example) Quincy Center. Visit the (for example) Quincy Center page. Observe that the No Service badge is no longer there.

Create a station bypass affecting all trains on (for example) the Fairmount Line at (for example) Uphams Corner. Visit the (for example) Upham's Corner page. Observe that the No Service badges are still there.