Previously the Dart entry points weren't wired up.

This fixes this Fuchsia build, which uses the latest //lib/ftl.

This transport uses the Dart and JNI APIs directly instead of indirecting
through Mojo.

We only ever had one UIDelegate. We might as well have people use the Engine
interface directly.

This allows setting testonly=true for gtest in the Fuchsia build.

This patch moves the rest of the clients to use the new PointerData
transport.

This patch prepares us to switch sending semantics information over mojom to
using dart:ui directly. Currently the recorded information is dropped on the
floor, but that will improve in future patches.

Example: $ mojo:launcher mojo:spinning_square

Instead, clients should use host messaging.

We now use JNI rather than Mojo to transport pointer data from Java to Dart.
Also, fill in a few more of the pointer data fields from information in Java.

The UI thread does not have an EGL context, so attempting to delete an
SkImage on that thread will fail to delete the image's texture, resulting
in resource leaks

This is intended for use in flutter_driver tests

This is used by debugging features that export Skia picture files
(see shell/common/picture_serializer.cc)

It adds ~20kb to a build of libsky_shell.so on Android

Now the engine always gives values in physical pixels.

Fixes https://github.com/flutter/flutter/issues/5783

Long live pointer data packets.

Previously we got some punctuation wrong.

Update buildroot (for target triple) and boringssl (for Clang IAS) fixes for non-ARM platforms. (#3077)

Rather than using mojom to encode pointer data, we now encode and decode it
manually. A future patch will remove the mojom codepath once the framework is
updated.

gclient now uses this to decide whether to look at a dependent
repo's DEPS file, which is needed for buildtools.

See https://groups.google.com/a/chromium.org/forum/#!topic/chromium-dev/NsGSfdLaDMI
for more detail.