Use CADisplayLink.targetTimestamp to drive animations

[nishant-karajgikar]

The new flyTo implementation uses Date() directly. Which is not the most sophisticated way of handling timing in animations. We should use CADisplayLink.targetTimestamp instead.

Also applies to GestureDecelerationCameraAnimator. See #692 (comment)

Also applies to InterpolatedLocationProducer

Originally posted by @julianrex in #282 (comment)

[macdrevx]

https://developer.apple.com/documentation/quartzcore/optimizing_promotion_refresh_rates_for_iphone_13_pro_and_ipad_pro has some good explanation of how to use targetTimestamp

[macdrevx]

https://developer.apple.com/videos/play/wwdc2021/10147/ is also helpful.

One key takeaway is that switching to targetTimestamp isn't enough — we likely also need to use something like MTLCommandBuffer.present(_:atTime:) so that our content is drawn at the expected time when our display link is using a lower frame rate than the screen's actual refresh rate.

[macdrevx]

Possibly relevant: https://developer.apple.com/documentation/metal/drawable_objects/creating_a_custom_metal_view

[OdNairy]

Still actual

mapbox-maps-ios/Sources/MapboxMaps/Camera/FlyToCameraAnimator.swift

Line 168 in fb97a45

let elapsedTime = dateProvider.now.timeIntervalSince(startDate)