* test flutter create project dart file is properly formatted

* restore driver-test

* cleanup lint warnings

* address comment

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

* search up directories looking for the flutter root

@Hixie: as per our conversation, a little more concise.

* 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

* move driver create test to the flutter_tools package

* review comments

* allow flutter create to re-gen over an existing project

* add a regression test

* Add validity checks to create

* Adjust indent

And fix a zillion omissions this uncovered.

Returns 69 instead of 0 in the `create --out` part.
https://github.com/flutter/flutter/issues/1709

@devoncarew

rename to printTrace(), printStatus(), and printError()

1) Moved basic utility code into base/ directory to make it clear which code
   doesn't depend on Flutter-specific knowldge.
2) Move the CommandRunner subclasses into a runner/ directory because these
   aren't commands themselves.

Fixes #311

wrap up first daemon implementation

Increase the test timeout for the `init` test to 2 minutes (test was timing out downloading assets on appveyor).

remove a runInShell arg on windows when launching pub

I'm trying to get a feel for the code by writing some simple cleanup patches.

Also update tests to be compatible with the presence of iOS and add tests for list and install.

Refactor all the commands to be Commands from the Args package.  Also use CommandRunner for the top-level command.