core: sim: ignore overlapping scheduled points

[eckter]

Fix #7744

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 0% with 3 lines in your changes missing coverage. Please review.

Project coverage is 28.61%. Comparing base (09eead2) to head (4b033f9).
Report is 2 commits behind head on dev.

Files	Patch %	Lines
...r/sncf/osrd/standalone_sim/StandaloneSimulation.kt	0.00%	1 Missing and 2 partials ⚠️

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@             Coverage Diff              @@
##                dev    #7747      +/-   ##
============================================
- Coverage     28.62%   28.61%   -0.01%     
  Complexity     2038     2038              
============================================
  Files          1244     1244              
  Lines        153687   153671      -16     
  Branches       3012     3014       +2     
============================================
- Hits          43991    43976      -15     
+ Misses       107905   107902       -3     
- Partials       1791     1793       +2     

Flag	Coverage Δ
core	75.03% <0.00%> (-0.02%)	⬇️
editoast	72.11% <ø> (-0.04%)	⬇️
front	9.91% <ø> (-0.01%)	⬇️
gateway	2.41% <ø> (ø)
railjson_generator	87.49% <ø> (ø)
tests	72.93% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[bougue-pe]

It's OK to merge as-is, but I would make that warning as rare as possible with an early dedup on consecutive identical steps (probably with an info/debug log) to ease the monitoring and separate "legitimate" cases (weird input) from the suspect ones (internal core behavior).

Context: As discussed, this case from the issue is not about consecutive identical step, as they are separated by another separate step on the same block but not at the same place.
So here, the pathfinding is wrongly aggregating identical steps because intermediate ones are on the same block (to be adressed in #7761)

[eckter]

but I would make that warning as rare as possible with an early dedup on consecutive identical steps (probably with an info/debug log) to ease the monitoring and separate "legitimate" cases (weird input) from the suspect ones (internal core behavior).

I've added a simple check to dedup the scheduled items, but I've only merged the ones that are entirely identical (offset, time, stop duration, on stop signal)

[bougue-pe]

Thanks !