[Polish] Map UX Improvements

[pingzing]

• [ ] (Pushed to 1.2) When tapping on a MapIcon, or selecting a Stop on the Search Page, don't zoom the user any further out than they already are.
• [x] On Creators Update or higher on the phone, crank up our zoom amounts by 2-3. The new MapControl insists on zooming way out compared to the old one. Desktop seems okay still.
• [x] When switching to the Nearby pivot, snap the map to the user's location.
• [ ] (Pushed to 1.2) Revamp Lines UX so that you can expand view a Line's details.

[pingzing]

Note about zoom levels: This is actually really hard.

This is because we aren't using ZoomLevel directly. We're simulating it by creating a small bounding box around an individual point on the map, and then moving to that. We have to do that, because we need to be able to accommodate the FloatingPanel, and that's the only way to give a margin to the MapControl's SetView.

Possible solution: Figure out what a few breakpoints for which bounding box size maps to which zoomlevel (i.e. we know that a bounding box of .005 on Desktop maps to about 15.77 ZoomLevel). Using this mapping, we can track what our previous bounding box and zoomlevel were, and if our new bounding box forces us to zoom out, we can adjust as necessary.

[pingzing]

Alternate solution: Make the FloatingPanel's wide state...not float. It doesn't add much value, and it makes the map operations hellishly-complicated.

Doesn't address the narrow state though. Hm.

[pingzing]

Alternate alternate solution: Looking into the MapControl's TransformOrigin property: https://docs.microsoft.com/en-us/uwp/api/windows.ui.xaml.controls.maps.mapcontrol . We might be able to play with this and move the Y/X values around when the floating panels are open. That way we can avoid all the BoundingBox methods entirely.