Cardinal direction fix

[dnesbitt61]

Fix highway directional for singly digitized roads and for some cases on doubly digitized ways where a relation has a direction. This required changes to OSM parsing logic to handle the forward and backward direction and dding reverse way refs to OSMData.

When a singlely digitized edge has a forward and backward direction for the reference/relation the code that builds EdgeInfo (within Graphbuilder as well as Hierarchy and Shortcut builders) has to check if a different name occurs in opposing directions of an edge. If so, then when creating EdgeInfo a new EdgeInfo is forced to be created so that different names can be supported. This creates some extra duplication of shape, but the total increase in tile sizes for North America is modest.

Testing of route differences was performed (specifically using the highway cardinal direction routes).

• Add tests
• Review - you must request approval to merge any PR to master
• Add #fixes with the issue number that this PR addresses
• Generally use squash merge to rebase and clean comments before merging
• Update the changelog

Example 1

< BEFORE
< 2: Turn left onto Walnut Street/US 22.
> AFTER
> 2: Turn left onto Walnut Street/US 22 East.

Example 2

< BEFORE
< 2: Turn left onto Walnut Street/US 22.
> AFTER
> 2: Turn left onto Walnut Street/US 22 West.

[dgearhart]

just need to update changelog - otherwise 👍

[dgearhart]