fix(map-matching): Fix broken map matching for here traffic data

[aoles]

Pull Request Checklist

• 1. I have rebased the latest version of the master branch into my feature branch and all conflicts
  have been resolved.
• 2. I have added information about the change/addition to functionality to the CHANGELOG.md file under the
  [Unreleased] heading.
• 3. I have documented my code using JDocs tags.
• 4. I have removed unnecessary commented out code, imports and System.out.println statements.
• 5. I have written JUnit tests for any new methods/classes and ensured that they pass.
• 6. I have created API tests for any new functionality exposed to the API.
• 7. If changes/additions are made to the ors-config.json file, I have added these to the ors config documentation
  along with a short description of what it is for, and documented this in the Pull Request (below).
• 8. I have built graphs with my code of the Heidelberg.osm.gz file and run the api-tests with all test passing
• 9. I have referenced the Issue Number in the Pull Request (if the changes were from an issue).
• 10. For new features or changes involving building of graphs, I have tested on a larger dataset
  (at least Germany), and the graphs build without problems (i.e. no out-of-memory errors).
• 11. For new features or changes involving the graphbuilding process (i.e. changing encoders, updating the
  importer etc.), I have generated longer distance routes for the affected profiles with different options
  (avoid features, max weight etc.) and compared these with the routes of the same parameters and start/end
  points generated from the current live ORS.
  If there are differences then the reasoning for these MUST be documented in the pull request.
• 12. I have written in the Pull Request information about the changes made including their intended usage
  and why the change was needed.
• 13. For changes touching the API documentation, I have tested that the API playground renders correctly.

Information about the changes

Addresses the problem of traffic data not being matched to the graph which has been discovered when working on #1403.

[MichaelsJP]

@aoles Is this PR ready?

[aoles]

@MichaelsJP Yes, otherwise I wouldn't mark it as such.

[MichaelsJP]

@aoles Are you sure proceeding without having at least basic unit tests for hmm module?

[aoles]

Thanks @MichaelsJP! This is just a spin-off from #1403 meant to address some fundamental problems. Its main purpose is to restore some basic functionality around map patching in order to enable the implementation of API tests for routing with traffic. In fact, it is not even meant to be a complete solution to all of the problems, see e.g. #1434. Therefore, I believe any additional tests are beyond the scope of this PR.

To summarize, I'm quite positive about merging the PR. Proper evaluation of the correctness of the HMM module will happen in #1435, and any potential unit tests should probably be added there.

[MichaelsJP]

@aoles Please give a short heads-up on the status of this and what still needs to be done. Thanks ❤️

[aoles]

@MichaelsJP It's ready to be reviewed and merged since about two weeks now :) The API tests for #1403 were not meant to be part of this PR and will be implemented in a separate PR.