editoast: adapt conflicts endpoint to paced trains

[younesschrifi]

Close #10684

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

Attention: Patch coverage is 92.30769% with 1 line in your changes missing coverage. Please review.

Project coverage is 81.86%. Comparing base (8aaefd4) to head (35fb47b).
Report is 1 commits behind head on dev.

Files with missing lines	Patch %	Lines
...nt/src/applications/stdcm/utils/formatConflicts.ts	0.00%	1 Missing ⚠️

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

Additional details and impacted files

@@            Coverage Diff             @@
##              dev   #10685      +/-   ##
==========================================
- Coverage   81.86%   81.86%   -0.01%     
==========================================
  Files        1082     1082              
  Lines      107119   107123       +4     
  Branches      721      721              
==========================================
+ Hits        87694    87696       +2     
- Misses      19384    19386       +2     
  Partials       41       41              

Flag	Coverage Δ
editoast	74.32% <100.00%> (-0.01%)	⬇️
front	89.40% <80.00%> (ø)
gateway	2.18% <ø> (ø)
osrdyne	3.28% <ø> (ø)
railjson_generator	87.50% <ø> (ø)
tests	87.87% <ø> (ø)

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.

[flomonster]

LGTM

[shenriotpro]

LGTM for tests/

[eckter]

For core: seems like a simple renaming, I'm not checking further (I trust that this matches the new names used in the payload)

[Erashin]

Not that this shouldn't be merged, I trust everyone else's opinion on the matter (especially if you know the subject). But from the pov of someone who has no idea what's going on, I clearly don't have enough info on this pr: i don't know what a paced train is, the commit has no additional info, description same, linked issue same, and no additional linked issue for additional info.
I'm guessing this is a first PR to pave the way for the following paced train conflict logic that will come in another PR. But yeah, I wouldn't be against having a bit more info somewhere for this sort of PR :)
As for the core part, lgtm, the rename works, and the added field isn't used yet anyhow.

[emersion]

Yeah, agreed - I kind of realize we should've written down a design doc on the website for paced trains…

[Khoyo]

There's a confidential issue (https://github.com/osrd-project/osrd-confidential/issues/779). It should be cleaned up and put as a real osrd issue, and ideally we should have a design document on the website indeed.

[younesschrifi]

I agree with everyone and I apologize for the lack of information.
I added a description in the issue.
I already made a PR in osrd_website (CF Timetable V2) to describe the paced train model and I'm going to add more information on it.
Thanks for the reviews.

@eckter @emersion @Erashin @Khoyo

[SharglutDev]

Lgtm (for front part) and tested :)