Move the drive/run common stuff to RunCommandBase, rather than the
superclass which applies to everything.

Implement --no-resident (fixes
https://github.com/flutter/flutter/issues/5448). This is particularly
useful when running flutter from scripts.

Rename RunAndStayResident to ColdRunner.

...and add --diagnostic-port.

...and document port 0.

...now that we have generic methods, their types need to be specified too.

* proxy service extension calls through the daemon protocol

* add test for app.callServiceExtension

* pass additional named params to daemon run

* add a trailing comma

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.

* have flutter run --machine log to stdout

* add a test

* add docs; fix type annotation lint

* reapply handle new Observatory URL changes
Fixes https://github.com/flutter/flutter/issues/6843

* allow non numeric IPv4 addresses
Fixes https://github.com/flutter/flutter/issues/7051

https://github.com/flutter/flutter/commit/737a55ef3e47036220e72f3b3e17353d461b5fab

* Remove the workaround that pinned args to v0.13.6
This reverts most of the changes in commit 6331b6c8
* throw exception if exit code is not an integer
* rework command infrastructure to throw ToolExit when non-zero exitCode
* convert commands to return Future<Null>
* cleanup remaining commands to use throwToolExit for non-zero exit code
* remove isUnusual exception message
* add type annotations for updated args package

* convert flutter commands to use ToolExit for non-zero exit code
* add convenience method throwToolExit
* print ToolExit message iff not null

* make showElapsedTime default to true

* support nested progresses

* improve hot reload message

* rethrow

* add flutter run --machine flag
* refactor daemon stdin/out command stream/response
* extract daemon startApp method
* refactor flutter run --machine to call daemon.startApp

* add a pause parameter to the reload command

* encode OperationResult as json

* reverse isOk logic

* make app ids more unique

* in-line the uuid class

* refactor _run to runCmd

* replace requiresProjectRoot getter with call to commandValidator

* replace requiresDevice getter with call to findTargetDevice

* trace command requires a debug connection, not a device

* inline androidOnly getter

* rename command methods to verifyTheRunCmd and runCmd

* move common verification into BuildSubCommand

* rename deviceForCommand to device

* rename methods to verifyThenRunCommand and runCommand

part of https://github.com/flutter/flutter/issues/5789

* send the base uri back to debuggers

* add a fullRestart parameter to app.restart

* add await

* support hot mode from the daemon protocol

* move method params to constructor

* send the reload source command for ios simulators

* review changes

* rewrite w/ a completer

This prevents multiple simultaneous runs of the analyzer from stomping
over each other (e.g. multiple runs of 'update-packages'). Certain
long-lived commands (like analyze, run, logs) are exempted once they've
done enough work to be safe from most stomping action.

This still doesn't make us entirely safe from craziness, e.g. if you're
half way through an 'update-packages' run and you call 'git pull', who
knows what state you'll end up in. But there's only so much one can do.

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

* send supportsRestart flag when starting an app

* remove unused imports

* review comments

Also, make it clear the screen between results so it's more obvious
what's going on when you have new results (especially when you have
fixed everything).