editoast: add stdcm search environment model and endpoints

[Castavo]

close #8168

[codecov-commenter]

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

Codecov Report

Attention: Patch coverage is 87.00565% with 23 lines in your changes missing coverage. Please review.

Project coverage is 27.48%. Comparing base (4388f9d) to head (da38382).
Report is 28 commits behind head on dev.

Files	Patch %	Lines
editoast/src/tables.rs	22.22%	14 Missing ⚠️
...itoast/src/views/stdcm/stdcm_search_environment.rs	94.28%	4 Missing ⚠️
front/src/common/api/generatedEditoastApi.ts	90.69%	4 Missing ⚠️
editoast/src/modelsv2/stdcm_search_environment.rs	97.43%	1 Missing ⚠️

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

Additional details and impacted files

@@             Coverage Diff              @@
##                dev    #8257      +/-   ##
============================================
+ Coverage     27.18%   27.48%   +0.29%     
- Complexity     2127     2155      +28     
============================================
  Files          1310     1316       +6     
  Lines        157758   158158     +400     
  Branches       3256     3262       +6     
============================================
+ Hits          42887    43467     +580     
+ Misses       112891   112708     -183     
- Partials       1980     1983       +3     

Flag	Coverage Δ
core	75.53% <ø> (+0.03%)	⬆️
editoast	64.64% <85.82%> (+0.39%)	⬆️
front	10.45% <90.69%> (+0.06%)	⬆️
gateway	2.03% <ø> (ø)
railjson_generator	87.49% <ø> (ø)
tests	72.98% <ø> (-0.20%)	⬇️

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.

[woshilapin]

I'm not sure that I understand completely how it will be used. In the description of the migration, it's mentioned that the object will almost be a singleton. And most of the code does seems to reflect that. But the name of the function retrieve_latest almost gives you a hint that there might be other instances of the object ("if there is a latest, it's relative to others"). It might just be a naming problem.

Apart from that, very clean PR with lot of tests, thank you 🎉

[Castavo]

@woshilapin when designing this implem with @flomonster we considered making the sql table an actual singleton.
However, there is no builtin in way to achieve this, the most commonly found way is to add a column, add a UNIQUE constraint on it, and a value constraint so it can take only one value.

So we opted to not enforce the singleton-ness.

Thus, if by some manual manipulation, the database has several rows, the "retrieve" function handles it gracefully.

What do you think ?
If we stay with this current model, I can add a clearer docstring on why retrieve_latest isn't called retrieve

[Khoyo]

From the original goal of https://github.com/osrd-project/osrd-confidential/issues/481, don't we want to support multiple environments and select the correct one based on the requested date ? This seems to override all the envs every time a POST is made

[Castavo]

@Khoyo with @flomonster we discussed that there actually probably wasn't a need to keep history. We could decide to actually keep history and add indexes on the time windows fields.

However, given that there are no "ON DELETE" clauses on the fields (so the env can't be accidentally deleted), all objects referenced by the history wouldn't be deletable.