What's important about this code is that it's presenting services outside the
VM, not the particular technology used to present the services.

This patch is part of a sequence of patches towards fewer top-level libraries.
In this patch, the gesture libraries are combined into one gestures.dart
library.

Conflicts:
	examples/widgets/scale.dart

First pass at support for pinch gestures; panning issues (needs testing)

Conflicts:
	sky/packages/sky/lib/gestures/drag.dart

Conflicts:
	sky/packages/sky/lib/gestures/drag.dart

Factor out GlobalKeyWatcher

- Reorder the methods so they are closer to run order.
- Reindent the code to match style guide.

This also moves the logic that tracks what Widget is being watched into
GlobalKeyWatcher, and much simplifies Mimic based on this.

FlexAlignItems.stretch didn't stretch

Please use GestureDetector instead.

Move Drawer to GestureDetector

This fixes an issue in the stocks app in horizontal mode where you could both
scroll and drag the drawer at the same time.

RenderView has to be a singleton for sanity during tests, otherwise they
all end up in the dirty lists and we end up pumping all of them each frame.

AnimatedContainer isn't an AnimatedComponent.

Turns out it gets nothing out of inheriting from AnimatedComponent.

This widget has no client.

Clarify why we don't assert that ancestor != null.

Be more explicit about what's state in dismissable

Move _activeCardDragEndPoint near build() so it's more obvious that it
is part of the build state.

Make a couple of functions use setState() since they modify variables
that are used by build().

Add a more detailed comment to the empty setState() call, since those
are dubious in general and need explaining when they occur, lest people
start using them as magic incantations to Make Things Work.

Follow-up for #1140.

If a StatefulComponent marks itself dirty, gets rebuilt, then its parent
gets rebuilt, its parent will find that its child is from a newer
generation and hasn't changed. Previously, we considered two stateful
nodes to not be syncable even if they were the same; combined with the
way the "old" node looks like it's been put elsewhere (since it's
already been synced), we end up confused as to why the new node is
already mounted.

This fixes the problem by making the canSync logic consider two
identical nodes as syncable (since they are; syncChild() short-circuits
that case), and by changing syncChildren to consider identical nodes as
matches even if they are already synced.

This specifically improves the reporting of exceptions in syncChild(),
and makes the way we've been adding information to toStringName() less
ad-hoc and easier to extend.

Also:

 - don't mark a node as from the new generation if it is dirty, since we
   know it still has to be built.

 - establish the rule that you can't call setState() during initState()
   or build().

 - make syncChild() return early for unchanged children.

 - update the tests, including adding a new one.

Revert "MultiChildRenderObjectWrapper should take an Iterable instead of a List"

This reverts commit 7592213df29066cd357eaa4fffe4a19ed3bae189.

Surface all the constructor arguments of AnimationTiming in all its subclasses.
Remove some pointless casts.
Fix some typos.
Put constructors first in class declarations.
Remove some blank lines where they just confused the structure of the code.

Minor cleanups (spelling mistakes, unneeded casts)

Address more comments from #1153

Various and sundry code cleanup