Also, make sure that broken tests actually break the bots.

And add a test to make sure that keeps happening.

This also fixes some related problems affecting "flutter run":
  * FLXes built during AndroidDevice.startApp need to match the build mode
  * APKs should always be rebuilt if the build mode uses AOT compilation

* allow per-command analytics suppression

* rev the usage package dep

* handle an exit code from android n

* review comments

* rename service_protocol.dart to protocol_discovery.dart

* add a wrapper around the obs. protocol

* use json-rpc in run

* consolidate obs. code; implement flutter run --benchmark

* review comments

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

* send ext.flutter.exit

* listen for help restart, quit

* refactor into a separate class

Fixes #3835

Updates the analyze command to pass a package map to analysis rather than a file path.

This allows us to avoid creating a needless temporary `.packages` file and host directory and saves us a trip to disk to retrieve the contents when building our URI resolvers for analysis.

* avoid sending analytics on ci systems

* review comments

Introduces a new Dart analysis wrapper that works directly with the analyzer API (in favor of shelling out to a separate process).

Some consequences:

  * we no longer need to fear parts (simplifying our dart file gathering)
  * we can filter by error code (when needed), rather than by error strings
  * no more IO scraping
  * no need to generate `main()` or to run with `--package-warnings`
  * we now specify an analyzer (and linter) version in the pubspec (we’ll want to make sure this doesn’t diverge too far from the analyzer shipped with the SDK but it does give us some room to play with experimental builds)
  * no more (re)scanning of error source files (and so no more source cache)
  * should generally be a bit simpler and easier to maintain
  * runs a bit faster :)

* complain on missing entries in flutter.yaml

* change to a hard failure

This makes it easier to generate charts that show the engine time and
the framework time separately.

* fix analysis errors

* review comments; fix test

* re-add an export for debugPrint

@devoncarew @jason-simmons

Check the adb install output for errors and stop "flutter run" if package installation fails (#3672)

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

Fixes #3624

This currently requires a local build of the engine.

Run "flutter build aot" to build an AOT snapshot.
Run "flutter build apk --profile" to build a "profile mode" APK that uses AOT.