front: stdcm: in new interface with debug data, GET is often not centered to the right time frame

[eckter]

What happened?

When testing stdcm requests at random, the output train sometimes appeared to be missing from the space-time graph. But it was actually on a different day. For example the solution would span from 8:00 to 10:00 on Tuesday, the output would be centered on 8:00 to 10:00 on Monday.

What did you expect to happen?

The output should be centered on the new train

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

I don't have an exact request payload (but I can probably find one). Try random paths on realistic timetables.

What I feel improve the chances of it happening is having the output train span over two days, and not picking the first available date of the timetable.

On which environments the bug occurs?

Local

On which browser the bug occurs?

No response

OSRD version (top right corner Account button > Informations)

c1d34dd

[SharglutDev]

@clarani fixed by your recent PR ?