feat: add geometry field to RenderedFeature

[idompolo]

Summary

• RenderedFeature currently only exposes id and properties, discarding the geometry from native queryRenderedFeatures results
• This makes it impossible to get geographic coordinates of queried features (e.g., finding the nearest POI to camera center)
• Adds an optional geometry field (Map<String, Object?>?) to RenderedFeature and populates it on all platforms

Changes

Platform	File	Approach
Interface	queried_layer.dart	Add geometry field to RenderedFeature
Android	map_state.dart	Gson.toJson(feature.geometry()) → JSON parse
iOS	extensions.dart	MLNFeature.coordinate → {type: Point, coordinates: [lon, lat]}
Web	map_geojson_feature.dart + map_state.dart	Pass through JS geometry object via dartify()

Use case

final features = controller.featuresInRect(rect, layerIds: ['my-layer']);
for (final f in features) {
  final geom = f.geometry; // {type: Point, coordinates: [lon, lat]}
  if (geom != null) {
    final coords = geom['coordinates'] as List;
    final lon = (coords[0] as num).toDouble();
    final lat = (coords[1] as num).toDouble();
    // Now you can use the exact coordinates
  }
}

Test plan

• Verified on Android with custom vector tile source (featuresInRect + featuresAtPoint)
• iOS verification needed
• Web verification needed
• Backward compatible — geometry is optional, existing code unaffected

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 80.10%. Comparing base (1a0b042) to head (8f35325).

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[josxha]

@idompolo thanks for considering to contribute. I think that adding the geometry field is a good addition but according to the CI the changes have build errors.