Use mojo from the PDF extension instead of using an extension API.

Use mojo from the PDF extension instead of using an extension API.

This changes the two mime handler guests - the PDF extension and an
extension used for testing - to use mojo directly to obtain the stream
details. It also restricts adding mojo bindings to only extensions that
have the mojoPrivate API feature.
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation

[Sam McNally, 2016-10-11 07:03:18]

Description was changed from

==========
Use mojo from the PDF extension instead of using an extension API.

This changes the two mime handler guests - the PDF extension and an
extension used for testing - to use mojo directly to obtain the stream
details. It also restricts adding mojo bindings to only extensions that
have the mojoPrivate API feature.
==========

to

==========
Use mojo from the PDF extension instead of using an extension API.

This changes the two mime handler guests - the PDF extension and an
extension used for testing - to use mojo directly to obtain the stream
details. It also restricts adding mojo bindings to only extensions that
have the mojoPrivate API feature.
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation
==========

[Sam McNally, 2016-10-11 07:03:27]

The CQ bit was checked by sammc@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-10-11 07:03:42]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-10-11 07:14:26]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-10-11 07:14:27]

Dry run: Try jobs failed on following builders:
  chromium_presubmit on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)