Handle both invalid trigrams and uics as invalid op

[achrafmohye]

Closes #10116

[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 87.50%. Comparing base (9ddc06c) to head (8c32833).
Report is 89 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   #10471       +/-   ##
===========================================
+ Coverage   81.61%   87.50%    +5.89%     
===========================================
  Files        1067       31     -1036     
  Lines      105535     1537   -103998     
  Branches      727        0      -727     
===========================================
- Hits        86128     1345    -84783     
+ Misses      19366      192    -19174     
+ Partials       41        0       -41     

Flag	Coverage Δ
editoast	?
front	?
gateway	?
osrdyne	?
railjson_generator	87.50% <ø> (ø)
tests	?

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.

[Akctarus]

Tested, ty for this fix

[emersion]

Placeholder comment, just so that GitHub gets this PR off my TODO list :P

See the discussion above.

[emersion]

The new logic looks good!

It seems like the usePathfinding() hook has a similar bug: handleInvalidPathItems() there checks trigrams only. There is a TODO:

// TODO: we currently only handle invalid pathSteps with trigram. We will have to do it for trackOffset, opId and uic too.

Are you feeling up for adding a new commit to fix that bug and do something similar to the logic in this PR, or do you prefer to leave that for later?