ci, dev: remove frontend nginx version, dev stack with bundled front …

[ElysaSrc]

The goal of this PR is to simplify the stack by:

• Removing the nginx front image
• Using the gateway front image by default
• Removing various duplications between dockerfiles
• Adding a script to manage all the docker compose stuff

Due to a limitation in Docker Compose not supporting targeting custom targets inside other Dockerfile in additional contexts, I've moved a part of the building system for the front on the Gateway Dockerfile. Not ideal, but does the trick.

NOTE : Before merging we should modify the protrected branch requirement

[codecov-commenter]

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

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 81.82%. Comparing base (d651580) to head (a88e08a).
Report is 17 commits behind head on dev.

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

Additional details and impacted files

@@            Coverage Diff             @@
##              dev   #10502      +/-   ##
==========================================
+ Coverage   81.80%   81.82%   +0.01%     
==========================================
  Files        1073     1073              
  Lines      106604   106829     +225     
  Branches      730      730              
==========================================
+ Hits        87208    87410     +202     
- Misses      19357    19380      +23     
  Partials       39       39              

Flag	Coverage Δ
editoast	74.28% <ø> (-0.02%)	⬇️
front	89.34% <ø> (+<0.01%)	⬆️
gateway	2.18% <ø> (ø)
osrdyne	3.28% <ø> (ø)
railjson_generator	87.50% <ø> (ø)
tests	88.14% <ø> (+1.09%)	⬆️

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

Maybe we should delete the scripts/host-compose.sh file?

[ElysaSrc]

Various updates : the order of the overrides matters more than I thought, so I switched the way I pars env flags.

[bougue-pe]

Thanks! ❤️

Only tested and reviewed the script, and it suits my (core debug) need at least as well as before:
./osrd-compose host up -d --build osrdyne osrd-images jaeger gateway postgres valkey rabbitmq && cd editoast && diesel migration run (then launching aside editoast no-cache & single-worker + core single-worker)
Improving a "without-back" dev-ex (no-cache, single-worker, exclude service instead of include) is another topic.

[bougue-pe]

Why not naming it osrd-compose.sh?

[ElysaSrc]

For the sake of brevity

[bougue-pe]

OK.

Oh, forgot about this remark: should we document it in the main readme, then? (I'm OK to do this, once we agree on it, if you prefer)

[ElysaSrc]

I'd rather have it in the documentation than the readme since the instructions in the readme are still properly working for someone that is pulling the repository to start the project locally and we should cover the topic more than just "type this command".

Maybe we should add a page for "starting the development environment" with various scenarios depending on the components you'd like to work on ? Wdyt ?