Enable web integration tests in CI

[stuartmorgan]

• Adds web support to the drive-examples script comment
• Enables driving the web integration tests on master
• Moves web integration tests to the main Dockerfile image since recent Chrome support has been added to the driver

Pre-launch Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I read the Tree Hygiene wiki page, which explains my responsibilities.
• I read and followed the Flutter Style Guide and the C++, Objective-C, Java style guides.
• I signed the CLA.
• The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
• I listed at least one issue that this PR fixes in the description above.
• I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.
• I updated CHANGELOG.md to add a description of the change.
• I updated/added relevant documentation (doc comments with ///).
• I added new tests to check the change I am making or feature I am adding, or Hixie said the PR is test exempt.
• All existing and new tests are passing.

[ditman]

This doesn't seem to be running all the tests that are available? I was probably not self-consistent with naming files? :/

[stuartmorgan]

This doesn't seem to be running all the tests that are available? I was probably not self-consistent with naming files? :/

Capturing from Discord for posterity: the script requires that the driver file end in _test.dart; many web examples use integration_driver.dart instead. That will be fixed separately.

(I think there's a bug in the script where that failure skips more code than its supposed to, as there's logging later on about not being able to find a driver that's not reached.) I misread, that's if it can't figure out what tests to drive. But we should potentially log about name mismatches at this level.)