Modify stops on routes for CR-Newburyport and CR-Franklin

[lemald]

Summary of changes

Asana Ticket: Review V3 API stop list and order for certain Commuter Rail routes

The details are all in the ticket, but more succinctly, this PR accomplishes three basic changes:

1. Removing Wonderland and Lynn (non-interim) from CR-Newburyport by excluding the local shuttle from consideration for stops on the route.
2. Fixing the ordering of Foxboro station on the CR-Franklin line, in both directions.
3. Making sure that the Fairmount Line stops show up on CR-Franklin by explicitly including the route patterns for Forge Park <-> South Station via Fairmount in consideration.

[rudiejd]

1 seems set 👍 .

for 2 and 3: comparing franklin devgreen stops to franklin prod stops - looks like the forge park to south station stops are now included. but this doesn't seem to match the order here - https://www.notion.so/mbta-downtown-crossing/Alerts-Manager-CR-stop-list-order-183f5d8d11ea80429999f95859abc372#2ecf5d8d11ea80acad71f33d26ff31e5?

[lemald]

Weird, the order looks fine if you specify direction_id=0 but it's wrong if you specify direction_id=1, and I don't think there's any material difference in how the two directional stop order overrides work. I'll have to look into it some more.

[lemald]

@rudiejd I ended up taking the option of just specifying the stop ordering for the entire line in direction ID 1 since nothing else was working. Let me know what you think.

[lemald]

Actually, that isn't quite right, it still sorts Hyde Park to the very end despite the overrides. Sorry, I'll have to keep looking into this.