fix(api-tests): Test based on mock 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.

Fixes #1403.
Also: some further improvements on #1430

Information about the changes

API test for the functionality of traffic-enabled routing based on HERE-like traffic data.

[aoles]

Not sure why the API test still fails on the GitHub runner, as for me it passes locally.

[aoles]

The API test fails on the GitHub runner with the following:

Error:    ResultTest.testTrafficSpeed:3656 1 expectation failed.
JSON path routes[0].summary.duration doesn't match.
Expected: is a numeric value within <1.0> of <495.0>
  Actual: <477.9>

The failure could be related to the fact that the server on which the API test is being executed uses a different time zone than the internally hard coded "Europe/Berlin".

[aoles]

So far I had no luck in reproducing the error locally by changing the local time zone on the machine on which the test is being executed.

With the "fix" introducing multiple snapping points it fails for me locally too 🙈

[aoles]

With the updated test dataset the reported difference is now:

Error:    ResultTest.testTrafficSpeed:3656 1 expectation failed.
JSON path routes[0].summary.duration doesn't match.
Expected: is a numeric value within <1.0> of <495.0>
  Actual: <337.0>

[MichaelsJP]

LGTM