core: pathfinding: tracks/waypoints aren't included when they are at the edge of the last track

[eckter]

What happened?

When running a pathfinding with the end waypoint at offset=0, the last track isn't included in the result. The last waypoint is placed on the previous track and isn't identified as the operational point.

What did you expect to happen?

The track path should include a 0-length track range covering exactly the waypoint. The operational point placed there should be identified.

How can we reproduce it (as minimally and precisely as possible)?

Find an operational point with an offset=0 and use it as last waypoint for a path

What operating system, browser and environment are you using?

• Env: Local

OSRD version (top right corner Account button > Informations)

fb39845