Make route parsing options dynamic in viewport data source

Some of the options in the viewport data source are "static" in a sense that they only take effect when a route changes (MapboxNavigationViewportDataSource#onRouteChanged). Namely:

• options.followingFrameOptions.intersectionDensityCalculation.minimumDistanceBetweenIntersections
• options.followingFrameOptions.frameGeometryAfterManeuver.distanceToCoalesceCompoundManeuvers
• options.followingFrameOptions.frameGeometryAfterManeuver.distanceToFrameAfterManeuver

Now, the route geometry is parsed once when it's provided and resulting geometries for all steps are cached. We could explore a lazy loading approach where we generate and cache only the route geometries for the upcoming step (as long as the options don't change) to make the above options also respected "dynamically".

cc @MaximAlien

Start with MapboxNavigationViewportDataSource#onRouteChanged and trace how route geometry is parsed and cached for all steps. Evaluate a lazy approach that caches geometry for the upcoming step while options remain unchanged, then verify that the three listed options are respected after they change without a route change.