Expose camera padding option

[LukasPaczos]

Closes #15436.

This PR exposes CameraPosition#padding and a bunch of utility methods around it. This gives a choice to set the padding lazily with MapboxMap#setPadding or immediately with MapboxMap#moveCamera(paddingTo(0, value, 0, 0)).

For example, both of the below will have the same effect:

mapboxMap.setPadding(0, 500, 0, 0);
mapboxMap.moveCamera(CameraUpdateFactory.newCameraPosition(mapboxMap.getCameraPosition()));

mapboxMap.moveCamera(CameraUpdateFactory.paddingTo(0, 500, 0, 0));

Additionally, this PR deprecates the lazy padding setters in favor of the camera property because now, the camera object can server use cases like what's mentioned in #15412 (comment):

We're navigating with top padding applied (0, 0, value, 0), the user clicks a POI and camera should travel to the POI that's centered on the screen. With the current behavior, the camera would jump when padding (0, 0, 0, 0) is applied to achieve that.

for example:

mapboxMap.moveCamera(CameraUpdateFactory.paddingTo(0, 1000, 0, 0));
mapboxMap.addOnMapClickListener(new MapboxMap.OnMapClickListener() {
  @Override
  public boolean onMapClick(@NonNull LatLng point) {
    mapboxMap.animateCamera(CameraUpdateFactory.newLatLngPadding(point, 0, 0, 0, 0));
    return false;
  }
});

/cc @astojilj

[tobrun]

Looking good, can we add @Size annotations to the padding[] public API setters?

[tobrun]

Besides the removal of using Espresso in the animation tests this is ready to ship.
Let's do that as tail work of this PR.