Add more turn lane configurations

[1ec5]

LaneView now supports the additional turn lane icon assets introduced in mapbox/navigation-ui-resources#21, including the combination U-turn–left turn that’s so common in the iOS simulator’s home of Cupertino:

As seen in the screenshot, some of the wider U-turn-laden icons get cropped even though they don’t bleed over the edge of the canvas in PaintCode. It’s probably a layout issue in LaneView or LanesView. (Ignore the fact that the number 2 lane is highlighted as a valid lane; that seems to be a bug in OSRM that isn’t present in a Valhalla-based Directions API endpoint. I’m guessing OSRM isn’t recognizing the divided intersection, so it thinks there are two very closely spaced left turns, the first of which can use either left turn lane.)

Unfortunately, I was unable to meaningfully update LaneViewTests, because it’s part of MapboxNavigationTests, which don’t run as part of SPM builds due to #2791 and don’t run as part of Carthage builds due to a lack of support for Carthage in MapboxNavigation. All I was able to do there was to incorporate some renames that took place internally in LaneView, but there are no test cases to exercise the new assets.

More to come:

• Import a new LanesStyleKit from PaintCode
• Remove limitations on the output of LaneIndication.ranked(favoring:)
• Add cases to LaneConfiguration that reflect the expanded repertoire of assets
• Add cases to LaneView.draw(_:) for calling the new LanesStyleKit methods
• Consolidate similar cases in LaneConfiguration(rankedIndications:drivingSide:)
• Update LaneViewTests
• Fix cropping of some of the wider icons
• Update the changelog

Fixes #576.

/cc @mapbox/navigation-ios @abhishek1508 @avi-c

[avi-c]

I have verified that the dual-use icons are now composited correctly and that the "slight" turn variants are shown correctly. I haven't been able to verify all the combinations in the simulator, but I believe we can merge this and deal with any specific issues as they pop up.

[avi-c]

Passes my test cases and the code looks good. Hopefully we can simplify this soon using additional context from the Directions API.