Fix harvard upper busway stop ids

[PaulJKim]

Summary of changes

Asana Ticket: Fix up Harvard upper busway stops (third time's the charm!)

Fix stop ids after BNR initial launch

[robbie-sundstrom]

LGTM! Next step would be a follow-up PR to signs-ui I believe?

[PaulJKim]

@robbie-sundstrom nope no need for a signs UI pr! Once this goes out, we'll start sending the missing predictions to the harvard busway sign right away. Signs UI just acts as a viewer for us to visualize what we're sending out to signs, along with some controls that OIOs use to set signs into different modes and configure headway values etc.

[digitalcora]

@PaulJKim It is part of the PR checklist that changes to signs.json here should also be propagated to SignsUI. Maybe there are some categories of change to signs.json that don't have any effect on the way SignsUI uses the file, but I'm not sure off-hand if this is one of those. Do you have a better handle on this?

[PaulJKim]

Ah, you're right - we should update the dependency in Signs UI so that prediction suppression works for the new stop_ids. Sorry @robbie-sundstrom, you were correct!

[PaulJKim]

Well actually, we don't include the busway signs in the stop_id to sign mapping so we don't need to update the RTS dependency here since it won't affect signs UI