See https://github.com/flutter/flutter/issues/11051

Eliminates the need for the device/daemon code to get at the iOS/Android
tooling indirectly via Doctor. In tests, we now inject the workflow
objects (or mocks) directly.

Should be reverted when https://github.com/flutter/flutter/issues/6577
is fixed.

* add min version checks for IntelliJ

* validate the installed versions of IntelliJ and the flutter plugin

* review comments

* Revert "Test installation status when ideviceid is not installed (#10254)"

This reverts commit 0e5d4a87.

* Revert "Partial rollback of #10204 (#10256)"

This reverts commit b291bf5d.

This broke Fuchsia as they haven't updated to Dart 1.24 yet :(

This helps to debug encoding issues that are believed to only happen for certain locales (see https://github.com/flutter/flutter/issues/10198 fo example).

DO NOT SUBMIT until Dart SDK has been bumped (https://github.com/flutter/flutter/pull/10110) as this depends on new API.

Add a flutter doctor --android-licenses command that locates and runs the Android SDK license manager (#9892)

See https://github.com/flutter/flutter/issues/8438

`adb` can sometimes hang, which will in turn hang the Dart isolate if
we're using `Process.runSync()`. This changes many of the `Device` methods
to return `Future<T>` in order to allow them to use the async process
methods. A future change will add timeouts to the associated calls so
that we can properly alert the user to the hung `adb` process.

This is work towards #7102, #9567

Fixes #6207

macOS counterpart to c670cd9e.

* Revert "Eliminate CocoaPods install step (#8694)"

This reverts commit f4a13bc7.

If the developer is relying on CocoaPods and hasn't done a pod install, we will do it for them. This is needed for a smooth native plugin experience, similar to what Gradle is doing on the Android side.

There's no hard dependency on CocoaPods. We only run pod install if the project uses CocoaPods, so developers are still free to use alternatives if they prefer (and if they don't want to use native plugins).

Fixes #8685
Fixes #8657
Fixes #8526

* Require CocoaPods 1.0.0 or newer.

And make sure we don't get a crash if running `pod install` fails.

* Address review feedback

* fix a doctor check for webstorm

* fix a missing reference

* Teach flutter tools to find gradle

Flutter tools will now use Gradle from Android Studio, which is now found automatically.

flutter doctor will verify that Android Studio has been installed, and that the included Gradle is at least version 2.14.1.

It is still possible to manually configure the path to Android Studio (flutter config --android-studio-dir=XXX) or Gradle (flutter config --gradle-dir=XXX), but this should only be necessary if they're installed somewhere non-standard.

Only tested on Linux and macOS for now.

Fixes #8131

Replaces unprintable characters with alternative symbols.

Replace version-specific link with a version-independent URL.

* fix issue detecting ios-deploy. fix issue matching IntelliJ Ultimate on Mac

* refactor directory navigation code

fixes https://github.com/flutter/flutter/issues/7654

Follow-up to #7625

Required for https://github.com/flutter/flutter/issues/138

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.