[core] Attempt constraining Y axis ratio first, then X axis

[brunoabinader]

This matches GL JS default constraint for the map boundaries. Parity ensured via newly added {basic,bright,satellite}-v9/z0-wide render tests.

[brunoabinader]

@mourner even though GL JS and Native are now in sync with regards to the transform constraint results, the heatmap produced by GL native is now different - it actually looks more correct as the color ramp is more pronounced - could you please check these render tests results and check -
( https://141939-16286131-gh.circle-artifacts.com/0/render-tests )? My suspicion is that this has shown a bug in GL JS side.

[mourner]

Not sure what's exactly going on but it might be a bug in GL Native — the heatmap is more intense likely because there are two points (original and duplicate from another tile) on top of each other.

[brunoabinader]

Not sure what's exactly going on but it might be a bug in GL Native — the heatmap is more intense likely because there are two points (original and duplicate from another tile) on top of each other.

I've revisited this and found out that GL JS uses the following logic: Attempt to constrain the Y axis if its scale (height / tile size) is bigger than 1 - if not, attempt constrain the X axis instead.

Updating this new logic in GL Native fixes the render test results. @mourner could you please re-review?