Check map maxBounds in Geolocate control

[ThisIsOstad]

Launch Checklist

Changes:
The GeolocateControl with a maxBounds set on the map when a user is located outside of the maxBounds, keeps trying to move the camera outside of the maxBounds and causes a bad experience for users. In this PR, I checked map maxBounds on geolocate success callback and if the located position is out of maxBounds, remove location dot marker, update control classList, emit an event called outofmaxbounds and return to avoid camera update.

Related issue: #4872

• briefly describe the changes in this PR
• write tests for all new functionality
• document any changes to public APIs
• post benchmark scores
• manually test the debug page
• tagged @mapbox/studio and/or @mapbox/maps-design if this PR includes style spec changes
• tagged @mapbox/gl-native if this PR includes shader changes or needs a native port

[andrewharvey]

This won't entirely fix #4872, since the underlying issue there is requesting a flyTo outside the maxBounds is currently undefined behaviour, so that would need to be resolved to close #4872.

If we decide in #4872 to require the API user to make their own check, then in my opinion this proposed solution is the way to go. We make that check first internally in GeolocateControl, and then only flyTo if it's valid, and then emit an error back to the API user so they can decide what to do (like show an alert), exactly how you've done this PR.

In lieu of a decision on #4872, I think it's good to implement this PR even if just for the time being (although based on my comment at #4872 (comment), I do think this is probably the right approach).

[andrewharvey]

This change looks good to me. I think emitting an event is the right way to handle this.

[andrewharvey]

cc @ryanhamley I'm happy with this change, are we good to merge or should I wait for someone from Mapbox to have a chance to review?

[ryanhamley]

Looks good to me! Thanks @MoradiDavijani and @andrewharvey