[webdev] Update canary default setting in Configuration (#2870) The `canaryFeatures` flag now defaults to `true` to match the expected value for the `moduleFormat` default. New coercions based on the expected intent when setting other flags: * Passing `--web-hot-reload` coerces canary mode to `true`. * Setting 'amd' module format coerces canary mode to `false`. The existing tests were passing because they always set the module format and canary flags explicitly. The actual usage in VSCode saw the `canaryFeatures` flag default value in some code paths leading to inconsistent settings. Fixes: https://github.com/dart-lang/webdev/issues/2869
| Package | Description | Version |
|---|---|---|
| dwds | A service that proxies between the Chrome debug protocol and the Dart VM service protocol. |  |
| frontend_server_client | Client code to start and interact with the frontend_server compiler from the Dart SDK. |  |
| webdev | A CLI for Dart web development. Provides an easy and consistent set of features for users and tools to build and deploy web applications with Dart. |  |
For information about our publishing automation and release process, see https://github.com/dart-lang/ecosystem/wiki/Publishing-automation.