iOS: add flyToCamera edgePadding+peakAltitude overload

[nagisa77]

Summary

• add a new iOS API overload: flyToCamera:edgePadding:withDuration:peakAltitude:completionHandler:
• route existing flyToCamera:withDuration:peakAltitude:completionHandler: and flyToCamera:edgePadding:withDuration:completionHandler: through the new overload to keep behavior consistent
• use shared inset combination logic (MLNEdgeInsetsInsetEdgeInset) for contentInset + edgePadding
• add tests covering the new API for completion callback and effective camera padding behavior

Why

Issue #791 requests parity with setCamera(... edgePadding ...) so fly transitions can also accept camera edge padding. While an edgePadding-only fly API exists, there was no public overload that combines edgePadding and peakAltitude.

User/Developer Impact

• iOS developers can now fly to a camera while specifying both transient edge padding and a peak altitude in one call.
• existing fly APIs remain unchanged and now share one internal path.

Root Cause

The fly API surface exposed peakAltitude and edgePadding separately, but not together, even though the internal implementation (_flyToCamera) already supports both.

Validation

• Added MLNMapViewGestureRecognizerTests::testFlyToCameraWithEdgePaddingAndPeakAltitude
• Added MLNCameraTransitionFinishTests::testFlyToCompletionHandlerWithEdgePaddingAndPeakAltitude