editoast: move train schedule base to schemas

[Wadjetz]

part of #7048

• Maybe rename TrainScheduleBase to TrainSchedule ?
• Move train schedule base to schemas
• Move tests to schemas
• Copy a json file exemple of train schedule for testing

[woshilapin]

Yeah, that the end of editoast/src/schema/v2/mod.rs 🎉 Thanks for the PR.

For the renaming of TrainScheduleBase into TrainSchedule, I agree with you, but let's wait for @leovalais to give an approval on that (he knows better than me).

[leovalais]

LGTM. Ping @flomonster for the renaming of TrainScheduleBase in TrainSchedule since he's the most involved with TrainScheduleV2. I'd be in favor of renaming unless there's a specific reason it was named this way.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

❗ No coverage uploaded for pull request base (dev@b3228a3). Click here to learn what that means.

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

Additional details and impacted files

@@          Coverage Diff           @@
##             dev    #7177   +/-   ##
======================================
  Coverage       ?   28.46%           
  Complexity     ?     2299           
======================================
  Files          ?     1154           
  Lines          ?   140044           
  Branches       ?     2845           
======================================
  Hits           ?    39867           
  Misses         ?    98527           
  Partials       ?     1650           

Flag	Coverage Δ
core	78.55% <ø> (?)
editoast	70.51% <100.00%> (?)
front	9.14% <ø> (?)
gateway	2.43% <ø> (?)
railjson_generator	87.49% <ø> (?)
tests	83.96% <ø> (?)

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.

[Wadjetz]

Hey @leovalais and @flomonster, let's merge this PR. It's blocking @hamz2a. We can make any potential modifications in another PR.