Do not throw when resolving a local engine if the .packages map does not include the flutter package (#5519)

* update the cache earlier

* add documentation

* make flutter run work with a pre-built apk

* refactor to remove the buildDir param

* This reverts commit 5e7e7b6e.

* default to lib/main.dart

This reverts commit 32ad81c8.

It can cause trouble if the user has a newer Android SDK installed normally.
Instead, just use the normal Android SDK.

* Fix `flutter upgrade`

* Fix builds on iOS

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

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).

* refactor the --resident run option into a separate file

* update daemon to run --resident apps

* re-plumbing daemon start

* send app logs

* update tests

* review changes

* fix test runner

* remove PackageMap.createGlobalInstance; rely on the ctor

* review comments

* resolve symlinks in paths to flutter

* review comments

This reverts commit 8f69cccc.

* dissallow -release mode on emulators

* have the help text print the default mode

This passes the information through Xcode to the `flutter build aot` call via
the environment so that it picks up the right artifacts.

Fixes #4186

* rebuild when the build type changes

* handle local engine builds

* also check the timestamp

* allow per-command analytics suppression

* rev the usage package dep

Artifacts from local engine builds will be found based on the --local-engine flag

Host tools can be found in the artifact cache directory for the host platform.
If a developer wants to use a local engine build instead, then provide an
--engine-build flag that selects the specific engine build variant.

* use vendored dart sdk; check the expected version of flutter

* search up directories looking for the flutter root

Update flutter_tools for the "unoptimized" engine build flag and the new output directory naming scheme (#3832)

* avoid sending analytics on ci systems

* review comments

* make the usage text more visible

* update the look of the usage text

* fix analysis errors

* review comments; fix test

* re-add an export for debugPrint

Also update the engine to a build where these tools have been uplaoded

* add google analytics

* send in the run target type

* track device type targets

* use the real GA code

* review comments

* rev to usage 2.0

* rev to 2.2.0 of usage; add tests

* review comments

This is currently hidden for development use.  It will select artifacts from
the android_{Debug,Release}_Deploy output in a local engine build.

* rename the --develop option to --debug

* fail if both --debug and --deploy are specified