Add delegate methods for tapping route duration.

[ShanMa1991]

Description

This PR is to fix #3847 by adding the ability for users to detect the taps on duration annotations for routes and continuous alternative routes.

Implementation

When users tapped the NavigationMapView, the NavigationMapView will check whether duration annotations for routes and continuous alternative routes have been tapped. If users tapped duration annotations, it will notify the NavigationMapViewDelegate.navigationMapView(_: didTap:) about the taps. If not, it will check the taps on Waypoints, the closest route and the closest continuous alternative route.

The NavigationMapViewDelegate.navigationMapView(_: didTap:) provides the route or continuous alternative route whose duration annotation has been tapped.

Screenshots or Gifs

[1ec5]

The user would tap on what visuallly appears to be the callout bubble. However, the callout bubble is offset from the actual feature data. This call queries for feature data located at the tap point, which would be some distance away from where the feature data is actually located.

For this approach to be more reliable than routes(closeTo:), we’d technically need to figure out the callout bubble’s screen rect. Alternatively, since we’re filtering to just the annotation layers, we could query for all the features in the current viewport, then select the result that’s closest to the tap point.

[1ec5]

@ShanMa1991 confirmed that these days, MapboxMap.queryRenderedFeatures(at:options:completion:) actually does account for label bounds and offsets. That’s a big deal. I think it resolves this concern and probably also some other issues in our backlog.

/ref #4165 (comment)

[1ec5]

A couple things that’ll prevent confusion down the line, but otherwise good to go.

[MaximAlien]

This method becomes more complex with time, I wonder if we could cover it with unit-tests to make sure that delegate methods are called based on expected priority.

[ShanMa1991]

Right now it still follows the previous sequence, but between the waypoints and route, it would check the duration annotation. I'll add test for this one later.