fix(android): apply edge insets to initial camera and watermark reliably

[lodev09]

Problem

Two Android edge-inset bugs, both visible on screens that reserve space for a bottom sheet via edgeInsets:

1. Initial camera ignores edge insets. onMapReady moved the camera to the initial position before applying padding. Unlike iOS (GMSMapView.padding repositions the camera target into the visible region), Android's setPadding never moves an already-set camera — so the initial camera centered in the full view instead of the inset viewport.

2. Watermark position is inconsistent. applyWatermarkTranslation assumed setPadding never repositions the watermark (fix(android): reposition Google watermark with edge insets #55) and translated it unconditionally. In practice the renderer sometimes repositions it — depending on renderer version and whether the watermark view existed when padding was set — so the manual translation either double-shifted the logo off-screen or, when the async GoogleWatermark lookup raced and missed, never applied at all.

Fix

• Apply edge insets before the initial moveCamera in onMapReady; camera updates after setPadding are relative to the padded center.
• Make the watermark translation measurement-based instead of assumption-based: read the watermark's layout position (excludes translation) relative to the map view and translate only for the remainder — 0 when the renderer already handled it, the full inset when it didn't (including lite/static mode, which never gets setPadding).
• Re-evaluate via an OnGlobalLayoutListener since the renderer adds and positions the watermark asynchronously; a target cache keyed on the watermark instance makes re-evaluations idempotent and avoids snapping in-flight animated inset changes.