Fix GL routes in signs.json

[PaulJKim]

Summary of changes

Asana Ticket: Investigate modifying headway destination based on (GL branch) service suspensions

In #663 we removed an old piece of logic that filtered predictions based off of the routes field in the source config. Now that that's gone, we don't need to do weird stuff in the signs.json file in order to get outlier predictions to show (ex. the occasional D train going down the Medford branch).

This change adjusts the routes fields for a handful of GL stations so that they accurately reflect what branches typically serve them. The change is also meant to set us up in anticipation of future logic for checking for downstream suspensions.

[github-actions]

Coverage of commit b20d80e

Summary coverage rate:
  lines......: 73.9% (1943 of 2631 lines)
  functions..: 79.4% (538 of 678 functions)
  branches...: no data found

Files changed coverage rate: n/a

Download coverage report

[github-actions]

Coverage of commit b20d80e

Summary coverage rate:
  lines......: 73.8% (1942 of 2631 lines)
  functions..: 79.4% (538 of 678 functions)
  branches...: no data found

Files changed coverage rate: n/a

Download coverage report

[panentheos]

Looks good.

[github-actions]

Coverage of commit 3cb437e

Summary coverage rate:
  lines......: 73.9% (1943 of 2631 lines)
  functions..: 79.4% (538 of 678 functions)
  branches...: no data found

Files changed coverage rate: n/a

Download coverage report