fix(google-maps): don't crash on a zero-width vector map

[Juice-de-Orange]

Closes #10596

Change List

• getViewPropsFromCoordinateTransformer: require positive width and height for aspect
• Unit test for a zero-width vector map

Fix and test are from @kaisermann's report (co-author on the commit). Verified with yarn vitest run --project=headless test/modules/google-maps/: the new test fails on master with the TypeError from the issue and passes with the fix. A temporary test running the 800x600 → 800x0 → 0x0 → 0x600 → 800x600 sequence from the issue no longer throws at 0x600.

---

Note

Low Risk
Single-line guard in vector-map view projection math plus a regression test; no auth, data, or API surface changes.

Overview
Fixes crashes when a vector Google Map is drawn at zero width (e.g. during resize) by hardening camera/projection setup in getViewPropsFromCoordinateTransformer.

Aspect ratio now uses width / height only when both dimensions are positive; otherwise it falls back to 1. The previous check only guarded on height, so a zero-width map with non-zero height could still produce an invalid aspect and throw during draw.

Adds a headless test that mounts GoogleMapsOverlay on a 0×600 vector map and asserts map.draw() does not throw.

^{Reviewed by Cursor Bugbot for commit ccb5b3f. Bugbot is set up for automated code reviews on this repo. Configure here.}

[greptile-apps]

Confidence Score: 5/5

[Medium impact] The PR appears safe to merge.

Summary

Prevents a zero-width Google vector map from producing a zero projection ratio.

• Zero-width vector maps draw without throwing.

_{Reviews (1) · Last reviewed commit: "fix(google-maps): don't crash on a zero-..." · Reviewed by Greptile}