Remove LatLng wrapping

[tobrun]

We initially added LatLng wrapping to be on par with logic exposed by the Google Maps SDK. Going forward we prefer having parity with core and gl-js. With next semver major update we are going to remove LatLng wrapping from the Android SDK.

[osana]

@tobrun @LukasPaczos

Just want to double check that with wrapping removed

The following code will create bounds: NorthEast 10, 170 and SouthWes -10, -170 which will be the opposite of what it was doing before as the shortest span (i.e.wrapping is not honored)
new LatLngBounds.Builder()
.include(new LatLng(10, -170))
.include(new LatLng(-10, 170))
.build();

[LukasPaczos]

This looks reasonable to me. With unwrapped values allowed, users can extend longitudes over 180/-180 and create short spanned bounds.