fix: Improved EdgeFinder in cases where adjacent connections share the same FROM and TO points

[schwepmo]

Description

• When using findClosestRoadPosition(GeoPoint geoPoint) ambiguities can arise if adjacent connections share the same FROM and TO nodes in opposite directions
• since we don't store information about the geometry of lanes, both edges can be a valid return and it depends on the KD-Tree, which edge is returned
• Additionally, a signature using the heading as a similarity measure for matching edges has been added to the EdgeFinder and has been propagated to the Routing and IRoutingModule interfaces
• I'm not sure what happens if two edges directly overlap

Issue(s) related to this PR

• Resolves internal issue 880

Affected parts of the online documentation

Changes in the documentation required?

Definition of Done

Prerequisites

• You have read CONTRIBUTING.md carefully.
• You have signed the Contributor License Agreement.
• Your GitHub user id is linked with your Eclipse Account.

Required

• The title of this merge request follows the scheme type(scope): description (in the style of Conventional Commits)
• You have assigned a suitable label to this pull request (e.g., enhancement, or bugfix)
• origin/main has been merged into your Fork.
• Coding guidelines have been followed (see CONTRIBUTING.md).
• All checks on GitHub pass.
• All tests on Jenkins pass.

Requested (can be enforced by maintainers)

• New functionality is covered by unit tests or integration tests. Code coverage must not decrease.
• If a bug has been fixed, a new unit test has been written (beforehand) to prove misbehavior
• There are no new SpotBugs warnings.

Special notes to reviewer