[WIP] Enable trainrun asymmetry

[louisgreiner]

In pair programming with @Yohh

Description

PR linked with issue on OSRD OpenRailAssociation repository : OpenRailAssociation/osrd#10576

PR work in progress, for exploration and review purposes

How to review properly

B) TrainrunSection arrival/departure time at nodes

Test all the different combinaisons of +/- 1 for the 5 different time values, and also for all locks combinaisons:

• leftDeparture / rightArrival / rightDeparture / leftArrival / travelTime
• leftLock / travelTimeLock / rightLock

left = source and right = target

C) Enable one-way trip

Warning

The return times (targetDeparture and sourceArrival) are only css-hidden, accordingly to the way NGE currently hides elements

Warning

Bug: when a trainrun is non-stopping at a node, the times for the trainrun dialog window are all hidden (because the target is not direct left/right)

D) Enable different travel times for round trips

Question: should we rename travelTime and returnTravelTime into forwardTravelTime and backwardTravelTime? I'm not a huge fan of backward, since we don't really go backward, rather forward also, but in another direction.

Remaining to do

Bugs:

• for C) fix display times for non-stopping nodes (see above)

Spread the features for the rest of the application:

• Pearls view (Perlenkette) doesn't take in account the above features, need to spread the changes to it:
  • B) TrainrunSection arrival/departure time at nodes
  • C) Enable one-way trip
  • D) Enable different travel times for round trips
• Space-time diagram (Streckengrafik) doesn't take in account the above features, need to spread the changes to it:
  • B) TrainrunSection arrival/departure time at nodes
  • C) Enable one-way trip
  • D) Enable different travel times for round trips
• For D), take in account non-stops for extractTravelTime()

List of features / fixes that would be nice to do if we have the time:

• Re-calculate symmetric values when symmetric toggle is hit
• Fix the conditional behaviour of TrainrunsectionValidator where we have set if (true) with a // TODO
• Documentation on code additions
• for B), when asymmetry is on
  • current behaviour: +/- 1 leftDepature and +/- 1 leftArrival change the same travelTime
  • target behaviour: +/- 1 leftDepature and +/- 1 leftArrival change a different travelTime
• fix behaviour when travelTime is reduced to 0
  • current behaviour: rounds to 0.1, then propagating to the other time values with decimal
  • target behaviour: goes to 60, not modifying the other time values
• For B) and C), use a toggle from SBB design system instead of checkbox
• Set custom input for node symmetry (something else than 60')
• Move roundTrip and symmetry checkbox to bottom of the dialog
• Set isSymmetry for whole trainrun at once

Issues

Checklist

• This PR contains a description of the changes I'm making
• I've read the Contribution Guidelines
• I've added tests for changes or features I've introduced
• I documented any high-level concepts I'm introducing in documentation/
• CI is currently green and this is ready for review