Feature: Merge consecutive walks at connection start or end at the service level

[munterfi]

Handle the case where a solution from the RaptorRouter has a walk transfer to a stop at the start or end of the connection, and then at the service level (ch.naviqore.service.gtfs.raptor.routing) another first or last mile walk is added to connect the target or source location.

Merge these two walks directly by using the walk calculator to calculate a walk from the public transit leg directly to the source or target location.

Affected are the following connection and isoline routing query templates: ConnectionGeoToGeo, ConnectionGeoToStop, ConnectionStopToGeo, IsolineGeoSource, e.g.:

@Override
    protected Connection postprocessConnection(GeoCoordinate source, ch.naviqore.raptor.Connection connection) {

        // TODO: Handle case where firstMile is not null and first leg is a transfer --> use walkCalculator
        // TODO: Handle case where lastMile is not null and last leg is a transfer --> use walkCalculator

        return switch (timeType) {
            case ARRIVAL -> {
                Walk lastMile = utils.createLastWalk(source, connection.getToStopId(), connection.getArrivalTime());
                yield utils.composeConnection(connection, lastMile);
            }
            case DEPARTURE -> {
                Walk firstMile = utils.createFirstWalk(source, connection.getFromStopId(),
                        connection.getDepartureTime());
                yield utils.composeConnection(firstMile, connection);
            }
        };
    }

TODOs

• Write failing test cases at the service level (e.g., in RoutingQueryFacadeIT).
• Implement an encapsulated solution which is reused in the query templates.