Replace getPointAnnotationsInBounds() w/ queryPointAnnotations()

[1ec5]

queryPointAnnotations() accepts a screen rectangle instead of a geographic bounding box. If you pass in the bounds (in screen coordinates) of a rotated, tilted map view, the query is restricted to the trapezoidal region visible in the map view.

Fixes #5151.

@jfirebaugh to review the C++ side. @tobrun to review the Java side, which I edited blind without a Java IDE. 😬

[1ec5]

This isn’t going to work: annotation views on iOS and marker views on Android work by inserting a point annotation that has no icon and is thus prevented from rendering at the GL level. But as the name suggests, queryRenderedFeatures() only returns GL-rendered features, so if the application is using only annotation views or marker views, this new method always returns an empty vector.

This approach will only work if we use querySourceFeatures(), which is unimplemented in mbgl but needed for parity with GL JS.

[1ec5]

It would be possible to hack around the issue by setting each annotation/marker view’s icon to a single transparent pixel. It’s unclear to me whether handling rotation and pitch is important enough to use such a hack.

[jfirebaugh]

assert(*feature.id <= std::numeric_limits<AnnotationID>::max())

[1ec5]

This will unblock #4838, #5467, #2082, and #5787.

[1ec5]

The issue in #5165 (comment) was resolved by associating every view-backed annotation with a spacer image: #5509.