Instead of targets/dart.dart -> targets/common.dart

Turn off flaky indicator for flutter_gallery__back_button_memory and flutter_gallery__memory_nav (#58838)

After updating the GBoard on the devicelab machines, these tests are no longer flaky.

8516b39dc Roll Dart SDK from 48b4528a44ac to 87c5e3612b70 (1 revision) (flutter/engine#18879) (#58935)

* 25bfe1147 Roll Dart SDK from 578fa6bee9eb to 4b9c2356e962 (1 revision) (flutter/engine#18871)

* 3f224d8e8 [nnbd] un-fork sky engine (flutter/engine#18830)

This reverts commit cce6b3c5.

* Send text error in JSON and print in tools

* Add test for error text

* Fix analysis issues

* Move streamListen to try/catch and use global.printStatus

* Extract print error fn and listen for events in web runner

* Add extension listen request to test

* Update packages/flutter_tools/lib/src/resident_runner.dart
Co-authored-by: Jonah Williams <jonahwilliams@google.com>

* Rename error parsing method

* Allow crash if listen for extension stream fails

* Add test for error and non-error extension events

* Fix formatting for TextTreeRenderer

* Use shorter message for second exceptions

* Specify types for map

* Add empty JSON for resident_web_runner test

* Move stream listen to vmservice and add vmservice test

* Fix stream type

* Move structured error log definition to vmservice

* Use correct test matcher isNot
Co-authored-by: Jonah Williams <jonahwilliams@google.com>

* fix cupertino page route dismisses hero transition when swipe to the edge

* add more comment

* addressing comments

* fix navigator observer announcement order

* addressing review comments

* update

* fix analyzer

[web & desktop] Hide all characters in a TextField, when obscureText is true on web & desktop (#56794)

This adds some information about the chosen device to the output log so that we can tell what type of device/OS Level/API Level the test is running on when doing a postmortem on a failed test.

So that we have a release where both are available without a deprecation warning.

Allow dumping sksl files on driver exit when a file path is provided to drive's --write-sksl-on-exit

Current versions of the Windows desktop build files don't require a specific Windows 10 SDK version, but doctor still checks for one since vswhere doesn't allow for flexible queries. This has been a common source of issues for people setting up on Windows for the first time, because the current VS installer by default only includes a newer version of the SDK than what doctor is looking for.

This removes the vswhere SDK check, and instead uses a manual check for SDKs. Since this uses undocumented (although fairly widely used, so relatively unlikely to change) registry information, the check is non-fatal, so that builds can progress even if the SDK isn't found by doctor; in practice, it's very unlikely that someone would install the C++ Windows development workload but remove the selected-by-default SDK from the install.

Now that all requirements are default, the instructions when missing VS have been simplified so that they no longer list individual components, and instead just say to include default items.

Fixes #50487

Make it possible for all FlutterCommands to be global free, by moving instantiation to inside the Zone context. Additionally, provide VerboseLogger and NotifyLogger (daemon) at the top level and remove from command-specific overrides.

This allows removing a work around where web devices needed to look up directly from the context in non-test code.

Technically the output preferences are still zone injected, but these will be moved soon as they were not being used correctly by the top level command (the injection comes after ArgParser reads the overflow values, causing numerous wrap issues)

This reverts commit 253eb1cf.

This reverts commit 720b7cb4.

This reverts commit bbe18f75.

Work towards removal of package:archive and ideally more stable unzipping of artifacts. These commands are available in Powershell 5+, which we already require for windows.