🚀 FEAT: Align spec for transit routing change features to new route

[e-lo]

As a user coding changes to transit stop permissions, dwell times, or hard coded transit travel times, I'd like to be able to code these as a transit routing change rather than having to delete the route and then re-add it as a new route

The way it is

Transit routing changes currently only have the ability to turn a stop on/off. Note that as currently specified in the spec it is a generic array, so could have more information, but it isn't built in to a specific representation.

transit_routing_change:
  service:...
  routing:
    existing:
     - 1
     - 2
     - 3
    set:
      - 1
      - -2
      - 3

Whereas new routes can specify:

• boarding: bool
• alighting: bool
• stop: bool
• time_to_next_node_sec: int
• dwell_sec: int

transit_route_addition:
  routes:
    - route_id: ...
      trips:
          headway_secs: ...
          routing:
            - 1:
                stop: true #when stop is set to True, defaults to allow both boarding and alighting
            - 2
            - 3:
                time_to_next_node_sec: 90
            - 4:
                stop: true # default to False, specify only when stopping
                alight: false  # default to True, specify only when not default
            - 5

Existing work-arounds

You can work-around this limitation by deleting a route and then re-adding it back in, although this would create different trip_ids.

The way it could be

transit_routing_change:
  service:...
  routing:
    existing:
     - 1
     - 2
     - 3
    set:
            - 1:
                stop: true #when stop is set to True, defaults to allow both boarding and alighting
            - 2
            - 3:
                time_to_next_node_sec: 90