Conveniences to Position model

[zugaldia]

This PR does two things:

• Adds a new Position.fromLngLat(double longitude, double latitude) method the be more explicit about the lat/lon order. It does not deprecate the Position.fromCoordinates() method as this is used for other cases too (e.g. set an altitude or a double array). Fixes Rename Position.fromCoordinate() to fromLngLat() #283.
• Adds a warning to the Position constructor if the lat/lon values seem out of range. Fixes Add Position check for correct order #266.

This last item is tested via the Test App. In MainActivity we create an object with values out of range and the warning can be seen as usual in the Android log window:

@cammace Please review.

[mention-bot]

@zugaldia, thanks for your PR! By analyzing the history of the files in this pull request, we identified @cammace and @ivovandongen to be potential reviewers.

[cammace]

👏 love the warning given now

[1ec5]

Position is still used with the Android SDK's runtime styling API, right? Note that out-of-range longitudes are expected for features that straddle the antimeridian.

[zugaldia]

@1ec5 Right, we're tracking a couple of antimeridian-related issues here.

[1ec5]

Yes, but doesn’t antimeridian straddling already work in the Android SDK? mapbox/mapbox-gl-native#6088 Or does that affect only annotations, which would use the SDK-specific model objects?