Get Mapillary Detections under a poweruser feature flag

[Bonkles]

Description

After speaking with Said about the object detections feature branch, we'll put it under a 'power user' feature and enable it in Rapid v2.

[Bonkles]

This work needs to be rebased on top of main, as it currently lives in the 2.0-derived branched called mly_objects_v2.

[Bonkles]

It would be a much nicer experience for the user if we could constrain the display of imagery points to ONLY those images that show a particular detection. This would greatly cut down on the visual clutter for mappers.

Bonus points: While an object is selected, the forward / backward < / > Buttons in the UI should go through the images that spot the object, not just advance the current road sequence. This would allow mappers to get a really quick contextual understanding of the feature and its alignment/correctness.

[Bonkles]

Conulted with @cbeddow about this, he did some research on the topic of 'only showing images that contain a detection', which would allow us to filter the images we display when an object is clicked.

According to his notes:

https://graph.mapillary.com/$MAP_FEATURE_ID?access_token=$TOKEN&fields=images

^ gives list of image IDs for that object, API Docs here: https://www.mapillary.com/developer/api-documentation#map-feature

Also:
https://graph.mapillary.com/$MAP_FEATURE_ID/detections?fields=value,image,geometry

For a map feature, this API call gives each image and detection geom, which I think is best displayed as a bbox of the detection in a bright color and not the unsimplified outline
^ right now I think we display too many detections (all of the outlines) and it would be better to get the bbox