* ignore exceptions from stdin.lineMode

* only catch IOException

It is now handled at a higher level for all commands.

Now that dart-lang/dartdoc#1236 is fixed.

This API was deprecated. Clients should use PlatformMessages instead.

As of Dart SDK 1.22.0-dev.5.0, `Process.exitCode` is no longer
mutable (that SDK version picks up https://github.com/dart-lang/sdk/commit/e5a16b1ca56414af3008afb8833660f95a9d06da).
This change allows the tools code to pass analysis in sdk versions both
before and after that change, to allow for analysis against both the host and
target sdks.

Also, make the exception handling for global key listeners slightly more
robust.

This reverts commit ef25a203 to unbreak the build.

* Bump Dart SDK to 1.22.0-dev.5.0.

* Suppress spurious `FutureOr` type warning.

* Fixed linter dep post merge.

* Formatting tweaks.

Change `Flexible`'s default `FlexFit`

Previously, `Flexible` defaulted to `FlexFit.tight`, which forced the child to
expand to fill the available space. Now, `Flexible` defaults to
`FlexFit.loose`, which does not force the child to expand to fill the available
space.

If you want the child to expand to fill the available space, consider using
`Expanded` instead.

Fixes #5169

We now produce a more reasonable error message when we're missing the
flutter_test dependency in a test. Also, remove the flutter_tools stack traces
when the engine dies.

Fixes #6187

Fixes #7413

Each stack trace will yield many async task stacks for every write request
that is in flight.  If the device side is unresponsive and all writes are
failing, then this can generate an overwhelming amount of logs.

This patch improves test coverage for a number of files that had low
coverage. This patch also fixes a few minor bugs found by these tests.

- [x] Wire up dependency checker and plumb flags down to the right place

Fixes #7014

Fixes #7375

Fixes https://github.com/flutter/flutter/issues/7351

When a test runs to completion, the test harness closes the stream side of the
StreamChannel, causing the sink side to be closed as well.  So by the time we
receive a test result of completed/harnessBailed, the controller sink has been
closed.

- better documentation

- verify (at run time) that onNotification doesn't return null, and
  report copious helpful information if it does.

- add a toString/debugFillDescription convention to Notification.

- actually test Notification

This confused me briefly the other day.

This patch adds a number of tests for previously untested lines.

* pass additional named params to daemon run

* add a trailing comma

Fixes https://github.com/flutter/flutter/issues/7210

This implements a new RenderViewport2 class to replace the existing
RenderViewport class.

This ensures that accidental usages of dart:io's
file API don't creep in over time.

This removes direct file access from within flutter_tools
in favor of using `package:file` via a `FileSystem` that's
accessed via the `ApplicationContext`.

This lays the groundwork for us to be able to easily swap
out the underlying file system when running Flutter tools,
which will be used to provide a record/replay file system,
analogous to what we have for process invocations.

Fixes #7372

Some clients pass null, which was previously allowed by Flexible.

Fixes #7383