[tool] Removes deprecated --web-renderer parameter.
Removes the --web-renderer option.
Flutter tool users won't be able to select their web renderer.
In order to not drop test coverage, tests are still run with the HTML Renderer, until its code is fully removed from the engine.
Part of https://github.com/flutter/flutter/issues/145954
Pre-launch Checklist
- [x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
- [x] I read the Tree Hygiene wiki page, which explains my responsibilities.
- [x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
- [x] I signed the CLA.
- [x] I listed at least one issue that this PR fixes in the description above.
- [ ] I updated/added relevant documentation (doc comments with
///). - [ ] I added new tests to check the change I am making, or this PR is test-exempt.
- [x] I followed the breaking change policy and added Data Driven Fixes where supported.
- [ ] All existing and new tests are passing.
If you need help, consider asking for advice on the #hackers-new channel on Discord.
Publishing this PR to have CI take a look. I fully expect this to fail.
The problem was that I was not using the correct renderer on flutter run/drive. Now I've corrected this (4a2ae1d), and tests should pass, unless I broke some by changing the errors. 🤞
In test_6, it seems the runner is doing:
`/work/flutter/flutter/bin/cache/flutter_web_sdk/ --incremental --target=dartdevc --experimental-emit-debug-metadata -DFLUTTER_WEB_AUTO_DETECT=false -DFLUTTER_WEB_USE_SKIA=false -DFLUTTER_WEB_USE_SKWASM=false -DDART_HHH_BOT=false -DFLUTTER_WEB_USE_SKIA=true --output-dill ...
That's probably not good :)
All right, down to 1 failing test!
All is green, I'll set this to autosubmit next week.