chore: Adjust Harvard upper busway config with new child stops/routes.

[cmaddox5]

Summary of changes

Asana Ticket: Fix up Harvard busway berth assignments

Updated Harvard upper busway config to account for new berth assignments.

Reviewer Checklist

• Meets ticket's acceptance criteria
• Any new or changed functions have typespecs
• Tests were added for any new functionality (don't just rely on Codecov)
• signs.json changes were also made in signs_ui
• This branch was deployed to the staging environment and is currently running with no unexpected increase in warnings, and no errors or crashes (compare on Splunk: staging vs. prod)

[panentheos]

The gist of this change looks correct, but the overall shape of this config looks incorrect, coming out of #809 . That PR added several new config entries, but they should probably have been added as additional source entries instead. Each config generates a separate row on the sign, so we typically want to collapse things by route, so each route gets one line.

We should fix this up so there are 9 configs, and they can have multiple sources if we need to e.g. support multiple stop ids for a route.

[cmaddox5]

The gist of this change looks correct, but the overall shape of this config looks incorrect, coming out of #809 . That PR added several new config entries, but they should probably have been added as additional source entries instead. Each config generates a separate row on the sign, so we typically want to collapse things by route, so each route gets one line.

We should fix this up so there are 9 configs, and they can have multiple sources if we need to e.g. support multiple stop ids for a route.

Ahh I see. That makes sense.

[panentheos]

Looks good, thanks!