Create paced trains model and add post and delete endpoints

[younesschrifi]

Close #10888

[codecov-commenter]

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

Codecov Report

Attention: Patch coverage is 94.21053% with 11 lines in your changes missing coverage. Please review.

Project coverage is 81.63%. Comparing base (0152d77) to head (e1d59ac).
Report is 81 commits behind head on dev.

Files with missing lines	Patch %	Lines
editoast/src/views/paced_train.rs	90.00%	4 Missing ⚠️
front/src/common/api/generatedEditoastApi.ts	73.33%	4 Missing ⚠️
editoast/src/views/timetable.rs	91.42%	3 Missing ⚠️

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

Additional details and impacted files

@@            Coverage Diff             @@
##              dev   #10842      +/-   ##
==========================================
- Coverage   82.57%   81.63%   -0.95%     
==========================================
  Files        1084     1098      +14     
  Lines      107404   110595    +3191     
  Branches      730      742      +12     
==========================================
+ Hits        88687    90279    +1592     
- Misses      18675    20274    +1599     
  Partials       42       42              

Flag	Coverage Δ
editoast	72.32% <96.00%> (-2.07%)	⬇️
front	90.22% <73.33%> (-0.26%)	⬇️
gateway	2.18% <ø> (ø)
osrdyne	2.98% <ø> (-0.31%)	⬇️
railjson_generator	87.58% <ø> (ø)
tests	87.90% <ø> (ø)

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.

[leovalais]

Cursory review.

I wonder if mod paced_train shouldn't be included in mod timetable since there's a bunch of visibility changes of existing definitions (that usually is a signal that something's wrong). (I know that we have DELETE /paced_trains and not DELETE /timetable/paced_trains, but URL path hierarchy and rust module trees are two different things that do not necessarily require correlation imo.)

Wdyt?

[younesschrifi]

Cursory review.

I wonder if mod paced_train shouldn't be included in mod timetable since there's a bunch of visibility changes of existing definitions (that usually is a signal that something's wrong). (I know that we have DELETE /paced_trains and not DELETE /timetable/paced_trains, but URL path hierarchy and rust module trees are two different things that do not necessarily require correlation imo.)

Wdyt?

don't totally agree. We'd like to use paced trains in cases where the timetable is decorelated, as will perhaps be the case with train schedules. Maybe there won't be such a case, and if it's not the case I think it's a good idea to put paced train in timetable, but we'd have to put train schedule there too, wouldn't we?

[leovalais]

We'd like to use paced trains in cases where the timetable is decorelated

I'm not saying we should change the URL scheme, DELETE /paced_train is fine for the reasons you mentioned. However nothing prevents us from putting mod paced_train in mod timetable as it can be convenient to share some definitions without compromising visibility (and locality).

What I'm trying to say is that the module tree doesn't necessarily have to match our URLs paths. We're currently a bit forced to do that because of the routes! macro, but if we had all the paths defined in a single file, we'd have no constraint on module trees whatsoever.

[woshilapin]

A first review, a few things are missing like indexes in the DB migration or the update of osrd_schemas.

[SharglutDev]

Lgtm (not tested)