core-editoast: stdcm: add work schedules

[eckter]

Fix #7335

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 56.75676% with 48 lines in your changes are missing coverage. Please review.

Project coverage is 29.35%. Comparing base (39c3cf8) to head (8f9325d).

Files	Patch %	Lines
editoast/src/views/v2/timetable/stdcm.rs	0.00%	40 Missing ⚠️
...in/fr/sncf/osrd/api/api_v2/stdcm/STDCMRequestV2.kt	57.14%	3 Missing ⚠️
tests/tests/utils/timetable.py	81.81%	2 Missing ⚠️
...n/fr/sncf/osrd/api/api_v2/stdcm/STDCMEndpointV2.kt	0.00%	1 Missing ⚠️
.../preprocessing/implementation/BlockAvailability.kt	95.23%	0 Missing and 1 partial ⚠️
editoast/src/core/v2/stdcm.rs	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    #7343      +/-   ##
============================================
+ Coverage     29.34%   29.35%   +0.01%     
- Complexity     2011     2012       +1     
============================================
  Files          1177     1177              
  Lines        145851   145957     +106     
  Branches       2865     2869       +4     
============================================
+ Hits          42800    42851      +51     
- Misses       101367   101421      +54     
- Partials       1684     1685       +1     

Flag	Coverage Δ
core	75.16% <86.84%> (+0.04%)	⬆️
editoast	72.31% <0.00%> (-0.14%)	⬇️
front	9.78% <ø> (ø)
gateway	2.41% <ø> (ø)
railjson_generator	87.49% <ø> (ø)
tests	84.29% <93.75%> (+0.32%)	⬆️

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.

[younesschrifi]

LGTM.
I just have one comment 🙂

[leovalais]

LGTM, not sure how to test it though (do we have an extract of work_schedules we can insert in the DB?).

A few naming nitpicks and a question (nothing blocking though 😄):

[eckter]

not sure how to test it though (do we have an extract of work_schedules we can insert in the DB?).

I've tested using the post /work_schedules/ endpoint. In fact I should probably turn that into a simple integration test.