[google_maps_flutter_web] Migrate to google_maps: 8.0.0

[Rexios80]

Migrates google_maps_flutter_web to google_maps: ^8.0.0

Blocked on the following:

• Fix issues with new js interop a14n/dart-google-maps#132
• [integration_test] Enable assertions when running with --wasm flutter#151426
• Fix flutter/packages tests that throw an error after test completion flutter#145149
• google_maps: 8.0.0 - TypeError: Cannot read properties of undefined (reading 'x') a14n/dart-google-maps#133
• [integration_test] flutter drive --wasm does not report results even though tests completed flutter#151561

Fixes flutter/flutter#148624

[Rexios80]

Why are the integration tests skipped? Is it because other steps are failing?

[stuartmorgan]

Why are the integration tests skipped? Is it because other steps are failing?

Because they are currently disabled

@ditman FYI in case you aren't aware; maybe something you could look at while gardening? @bparrishMines That's assigned to you, are you actively working on it? We shouldn't leave whole tests suites disabled for extended periods if we can avoid it.

[bparrishMines]

@stuartmorgan Yea im going to take a look into it now. I'll try to narrow down the specific test to skip, so we no longer skip all the integration tests.

[Rexios80]

@stuartmorgan is there an issue to track running integration tests compiled to WASM in CI?

[kevmoo]

you'll want to drop this override, I think

[Rexios80]

Definitely

[kevmoo]

We also likely DON'T want to publish this package depending on a pre-release package.

[Rexios80]

We also likely DON'T want to publish this package depending on a pre-release package.

Also definitely the case

[stuartmorgan]

@stuartmorgan is there an issue to track running integration tests compiled to WASM in CI?

@ditman would probably be the best person to answer this; I'm not sure what the current plans are around wasm support and testing for plugins.

[Rexios80]

I created flutter/flutter#151664 to track running web integration tests compiled to WASM

[kevmoo]

@Rexios80 – can we help you here?

[Rexios80]

@kevmoo
The biggest blocker for me personally is flutter/flutter#151426 because without that I can't even run the integration tests compiled to WASM locally. It would be cool if we could get CI running WASM integration tests before we land this but that might not be feasible. I think we will have enough fixing up to do when we try running all package integration tests compiled to WASM so I don't want to add to it if I can avoid it.

I have a deployed WASM site with these changes here: https://beta.madadmaps.com. The performance upgrade from Skia is unreal! I think @ditman is busy with other things right now so that's probably what's actually blocking this from landing.