[POC] Do not force usage of orthogonal edge segments

[tbouffard]

WIP unfiinished

covers #295 (and other related issues)
New attempt to reimplement #351

e2e tests are failing because

• threshold are not set for bpmn-rendering tests
• other tests have not been reviewed (in particular snapshots haven't been recreated)

[github-actions]

🎊 PR Preview f2e518d has been successfully built and deployed to https://process-analytics-bpmn-visualization-js-doc_preview-pr-1779.surge.sh

🕐 Build time: 40.082s

_{🤖 By surge-preview}

[github-actions]

🎊 PR Preview f2e518d has been successfully built and deployed to https://process-analytics-bpmn-visualization-js-demo_preview-pr-1779.surge.sh

🕐 Build time: 40.159s

_{🤖 By surge-preview}

[tbouffard]

Current status

The orthogonal segments are dropped, but we see side effects on sequence and message flow arrows. Depending on the zoom level, they are not aligned with the edge segments.
This can be seen directly by checking the e2e screenshots used for non regression visual testing.

For instance, the arrow of the message flow at the top right of the diagram of flows.message.01.icons-snap.png

Same for the arrow of the sequence flow at the right of the diagram of associations.and.annotations.01.general-snap.png

We also see issue like the one described in #351 (comment): we know this happens when the terminal waypoints are outside the shape. Same issue as for #715
See #1863 for an implementation that fixes the issue.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[tbouffard]

Closing, a new Pull Request will be created with the work started here and improvements available in #1863