Migrate classes to core navigation

[ericrwolfe]

Some of the following classes and logic would be useful to move over to MapboxCoreNavigation from the UI module, to give developers better building blocks for creating custom navigation apps from scratch:

• Distance formatter
• Location simulation
• Voice instruction formatting (should be extracted from voice controller) Extract text instruction generation from voice controllers #367
• Voice controller
• Location snapping Extract location snapping logic and move to core #373

cc @bsudekum @frederoni

[1ec5]

We performed the most straightforward parts of this task in #309 and #310. Moving to v0.6.0 for the rest.

[frederoni]

Voice instruction formatting (should be extracted from voice controller)

Requires adding OSRMTextInstructions.swift as a dependency to core navigation.

[ericrwolfe]

@frederoni seems like OSRMTextInstructions.swift is already a dependency of Core Navigation, at least in Cocoapods land:

mapbox-navigation-ios/MapboxCoreNavigation.podspec

Line 44 in c113e51

s.dependency "OSRMTextInstructions", "~> 0.2.0"

[1ec5]

Heh, that was probably an oversight, but I guess it’s OK to have Core Navigation depend on OSRM Text Instructions. The more important consideration is making Polly an optional dependency somehow, because the AWS dependencies are enormous compared to Core Navigation proper.

[bsudekum]

The checklist has been moved to core.