Fix stale test for choropleth fitbounds fallback behavior

The test asserted that any choroplethmap trace on the subplot forces
getMapFitBounds to return null. That was true before choroplethmap
support was added, but the added commit intentionally lets a
choroplethmap trace with unresolved geojson be skipped while other
traces still drive the fit, so the old assertion no longer matches
the documented behavior. Updated the test to check that case, and
added the real null case: a subplot where the only trace is a
choroplethmap with no resolvable geojson.

Author: kirthi-b

test/jasmine/tests/map_get_fit_bounds_test.js

@@ -149,9 +149,20 @@ describe('Test getMapFitBounds', () => {
         });
     });
 
-    it('returns null when a choroplethmap trace is present on the subplot', () => {
+    it('skips a choroplethmap trace whose geojson has not resolved yet, using the other traces for bounds', () => {
         const fullData = [scattermap({ lon: [-10, 10], lat: [30, 40] }), choroplethmap()];
-        // location-based traces need geojson bbox handling — bail entirely
+        // choroplethmap() has no geojson set, so it can't contribute a bbox and is skipped;
+        // the scattermap trace still drives the fit
+        expect(getMapFitBounds(fullData, 'map')).toEqual({
+            west: -10,
+            east: 10,
+            south: 30,
+            north: 40
+        });
+    });
+
+    it('returns null when the only visible trace is a choroplethmap with unresolved geojson', () => {
+        const fullData = [choroplethmap()];
         expect(getMapFitBounds(fullData, 'map')).toBe(null);
     });