Consider Wheelchair boarding/alightning when routing from or to directly to a stop

[TimMickelsonSkanetrafiken]

- If requested wheelchair trip, check on boarding/alightning if possible on stop
- Unit test Raptor wheelchair accessibility

Summary

If a trip search is done from a StopPoint to another and in GraphQl the parameter wheelhairAccessible is true then we find trips that should not be found because the stop is not considered accessible for wheelchair.

Issue

closes #4044

Unit tests

Unit test in Raptor module, new class following instructions in markup document. Test going between stops where one stop has no access for wheelchair.

[leonardehrenfried]

I think from a logic perspective this looks good.

I'm sure that @t2gran has some comments about the general architecture though.

[hannesj]

I think the filtering might be better done in RaptorRoutingRequestTransitDataCreator, so that we lift up the boardingPossible and alightingPossible Bitsets to TripPatternForDates. That way we could do a union between those from the pattern and wheelchairAccessible, if wheelchair is required, and otherwise just use the ones from the TripPatternWithRaptorStopIndexes. This would make it easier to do other types of similar filtering in the future, such as banned stops.

It might be sensible to add something to the TransitDataProviderFilter interface for this.

[t2gran]

Tip: As @hannesj writes passing information trough Raptor, changing the Raptor interfaces is a red flag. The interfaces define what information Raptor need to do the routing in a generic way - passing information through is possible without changing the interfaces. We try hard to avoid changing them. If a small feature like wheelchair routing can not be supported using the existing abstractions, then we think reel hard to and add a reusable abstraction/feature to Raptor. An example would be that wheelchair need extra board time depending on the trip, then we will add the ability to add extra board time to raptor - but we are not passing in a "wheelchair" flag to enable it, instead we make it pluggable.

[t2gran]

Earlier we had a stop filter in Raptor, but we removed it because we did not use it. It might be an idea to add that back for this - but I am not sure.

[t2gran]

I think this looks ok, just some minor stuff. A little confusing to find the entry point of this code, since it existed already.

[leonardehrenfried]

We merged #4007 recently which reformatted all files in the repo. This created a conflict with this PR - sorry about that.

Could you please resolve the conflicts and push an update?

His comments have been addressed.