google_maps_flutter has a combination of serious performance issues that make performant animated current overlays very difficult. Since we're not using the Google base map (yet) anyway, let's migrate to Flutter-side rendering. This vastly improves performance, gets rid of many rough edges, and allows us to move several tests from flake-risk native tests to reliable widget tests.
google_maps_flutterhas a combination of serious performance issues that make performant animated current overlays very difficult. Since we're not using the Google base map (yet) anyway, let's migrate to Flutter-side rendering. This vastly improves performance, gets rid of many rough edges, and allows us to move several tests from flake-risk native tests to reliable widget tests.Part of https://github.com/AsturaPhoenix/trip_planner_aquamarine/issues/41
Fixes https://github.com/AsturaPhoenix/trip_planner_aquamarine/issues/4 Fixes https://github.com/AsturaPhoenix/trip_planner_aquamarine/issues/22
Progress towards https://github.com/AsturaPhoenix/trip_planner_aquamarine/issues/9 Progress towards https://github.com/AsturaPhoenix/trip_planner_aquamarine/issues/14
Also applies the cachebusting workaround discussed at flutter/flutter#122695.