[Refacto]: Origin-destination matrix using source-target chain

[louisgreiner]

Preflight Checklist

• [x] I have read the Contributing Guidelines for this project.
• [x] I agree to follow the Code of Conduct that this project adheres to.
• [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.

Request type

Request for enhancement of a component

Functionality

Following of https://github.com/OpenRailAssociation/netzgrafik-editor-frontend/pull/521

Link to design proposal file

No response

[aiAdrian]

What is the goal of this task? Please add more ingos (describe the problem)

[louisgreiner]

A few commits ago (for one-way feature), we enforced the fact that the sections are now always chained like that: [source -- target] [source -- target] [source -- target] [source -- target]... -> this is easy to deal with and iterate along. This also highly simplify the code, each time we have to iterate on a trainrun the commit

Before that, trainruns could be chained like that: [target -- source] [source -- target] [target -- source] [source -- target]... -> this is difficult to deal with and iterate along

And currently, the OD algorithm iterates using the consecutiveTime (because it was implemented before the source->target chain). The idea would be to refactor using the source->target chain.

Is it more clear or do you need examples?