[ios] Don't pause camera animations if zoom/pitch/rotate/scroll are disabled

[captainbarbosa]

Closes #11415.

Currently when a camera animation is triggered programmatically, if the zoomEnabled / pitchEnabled / scrollEnabled / rotateEnabled are all set to NO/FALSE, user interaction causes the transition to stop. This PR reverses that decision, so that a programmatic camera transition will continue if the above four properties are set to NO/FALSE

[friedbunny]

What’s the MapKit behavior in this case, re: camera and user tracking?

[captainbarbosa]

@friedbunny see #11415 (comment) to check out my comparison from researching the behavior on other platforms:

I compared this behavior to some other maps SDKs, mainly Google Maps and MapKit. When the related is*Enabled property is set to false in MapKit, a user is still able to stop a programmatic camera transition when interacting with the display. The Google Maps SDK however, doesn't allow a user interaction to stop a camera transition when the associated *Gestures properties are set to false.

I went ahead and addressed your review and included the changelog entry as well.

[julianrex]

@tobrun what's the similar behavior on Android?

[tobrun]

@tobrun what's the similar behavior on Android?

We don't interrupt animations when user input is disabled

[julianrex]

@captainbarbosa @friedbunny Given that MapKit and Google differ, I think we should be consistent with our Android SDK.

[captainbarbosa]

👍 cool, so this PR more closely aligns the iOS SDK with our Android offerings. @friedbunny @julianrex could either of you do a final review?

[julianrex]

👍