OSM data links added to the graph build report about ambiguous levels and layers

[vesameskanen]

Summary

OSM level and layer processing generates lots of data issue reports. Those used to be fairly useless because the report did not specify which OSM entity had the problem.

Now each reported ambiquity contains a link to the OSM item.

[codecov]

Codecov Report

Attention: Patch coverage is 42.85714% with 8 lines in your changes missing coverage. Please review.

Project coverage is 69.74%. Comparing base (95415dc) to head (8cedc68).
Report is 32 commits behind head on dev-2.x.

Files with missing lines	Patch %	Lines
.../issues/FloorNumberUnknownGuessedFromAltitude.java	0.00%	3 Missing ⚠️
.../opentripplanner/openstreetmap/model/OSMLevel.java	25.00%	3 Missing ⚠️
...p/issues/FloorNumberUnknownAssumedGroundLevel.java	33.33%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             dev-2.x    #6049   +/-   ##
==========================================
  Coverage      69.74%   69.74%           
- Complexity     17318    17322    +4     
==========================================
  Files           1960     1960           
  Lines          74273    74271    -2     
  Branches        7605     7605           
==========================================
+ Hits           51800    51801    +1     
+ Misses         19830    19829    -1     
+ Partials        2643     2641    -2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.