Rename operational point fields for the international format

[ppitou]

Closes #16522
Closes #16519

Warning

The backend part of this PR is done and ready for review, the front part is still in progress

For the international format, the extensions have been flatten and some fields have been renamed:
Previous fields :

• trigram is now main_code
• ch is now secondary_code
• ch_long_label is now secondary_name

New fields :

• country_code : "FR" as example for the France
• is_passenger_station as a boolean

[github-actions]

⚠️ API changes

This Pull Request introduces some changes in the API:

• please own it: notify or even prepare dedicated PR(s) to consumer projects

Changes in Schemas

Dear @ppitou, please ensure the following:

• changes should match in osrd_schemas and editoast schemas
• the RailJSON version in osrd_schemas::infra.py and editoast schemas::infra::railjson.rs should match and be bumped on any change of infra schemas (same goes for rolling-stock between osrd_schemas::rolling_stock.py and editoast schemas::rolling_stock.rs)
• the version of the Python package in osrd_schemas::pyproject.toml should be bumped on any change

[hhirtz]

halfway through the front changes

[hhirtz]

review for the rest of the front changes

[hhirtz]

Going through all the comments, those are still unresolved:

• Rename operational point fields for the international format #16799 (comment)
  need to find a way to differentiate track offsets from ops i think?
• Rename operational point fields for the international format #16799 (comment) and Rename operational point fields for the international format #16799 (comment)
  do these two functions can be merged or not?