See https://github.com/flutter/flutter/pull/10000

* try use_to_and_as_if_applicable lint

* address review comments

If the caller doesn't explicitly give the brightness of the primary
color, we now estimate it using an algorithm from the Web Content
Accessibility Guidelines.

Also, this patch contains a function that converts RGB colors to
HSVColors. I was originally going to use that, but the WCAG algorithm
ended up seeming like a better choice. The patch still includes this
function because it's generally useful.

Fixes #5718

Fixes #9989

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

This way, you can test things even with a VerboseLogger.

During SDK version updates, output the commands used to tag the repo
with the SDK version.

The new assets have been optipng'ed.

Previously, we would strand the old route in the overlay even though it had
been removed from the history.

The default is topCenter, which is sensible, but someone might want to use a
bottomCenter alignment, for example.

VERSION: 0.0.7-dev
flutter: 0.0.27-dev
flutter_driver: 0.0.5-dev
flutter_test: 0.0.5-dev

VERSION: 0.0.6
flutter: 0.0.26
flutter_driver: 0.0.4
flutter_test: 0.0.4

Update Android package name.

Since lib/main.dart does not exist, update test to explicitly build lib/keyboard_resize.dart.

Adds an initial integration test that:
1. captures laid-out widget size
2. focuses a text field to show the keyboard and resize the view
3. unfocuses the text field to dismiss the keyboard and resize the view
4. verify that the final widget size matches the initial size

They are causing nothing but trouble. We should fix these before turning them back on.

See https://github.com/flutter/flutter/issues/9986 https://github.com/flutter/flutter/issues/9987

* Rev versions for alpha branch

* Rev versions after alpha

* is default

* hit target

* correct test name

* review note