Convert file_utilities_messages to mojo

Because we now have mojo I altered the API to return an optional FileInfo and
dropped FileError from the API entirely.

Added base::File::Info as a common mojo message so it's available for other
users in future, it already had the IPC code to serialize the messages.

Honored the existing task dispatch for messages on both sides, using a
ThreadSafe interface on the send side and a sequenced task runner on the
receiver side.

In a follow-up CL we can look at removing WebFileInfo as we *might* be able
to use base::File::Info for all of these use cases.

Bug: 765533
Change-Id: I161f22c1ae0ac4f47f856aa70b976727dc462324
Reviewed-on: https://chromium-review.googlesource.com/663005
Commit-Queue: Stuart Langley <slangley@chromium.org>
Reviewed-by: Sam McNally <sammc@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Noel Gordon <noel@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#504581}

CrOS-Libchrome-Original-Commit: e6f32c59b87f5fc8b029281a6b12ae512a093e89
3 files changed
tree: 7560432478373207ef0d2feba9448fe91a548804
  1. base/
  2. build/
  3. components/
  4. dbus/
  5. device/
  6. ipc/
  7. mojo/
  8. testing/
  9. third_party/
  10. ui/