Revert of Add Mojo interfaces for out-of-process proxy resolver.

Revert of Add Mojo interfaces for out-of-process proxy resolver. (patchset #4 id:60001 of https://codereview.chromium.org/900433003/)

Reason for revert:
http://build.chromium.org/p/chromium.linux/builders/Linux%20Tests%20%28dbg%29%281%29/builds/38575
Broke device_unittests device_unittests SerialConnectionTest.Cancel it seems.

Original issue's description:
> Add Mojo interfaces for out-of-process proxy resolver.
>
> See:
> https://docs.google.com/a/chromium.org/document/d/1n5hr4KJhZl2A4MicTfmyiHPdiKp7kmUoWXnRBN8SrZE/edit#
>
> BUG=11746
>
> Committed: https://crrev.com/073e42bb7587b90594e5799fb6a4afe08a1e1561
> Cr-Commit-Position: refs/heads/master@{#314509}

TBR=rdsmith@chromium.org,eroman@chromium.org,sammc@chromium.org,amistry@chromium.org
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=11746
Committed: https://crrev.com/7d4ec1aa24e79406d29e0cafbb531a3fabfe815f
Cr-Commit-Position: refs/heads/master@{#314519}

[Noel Gordon, 2015-02-04 07:37:06]

Created Revert of Add Mojo interfaces for out-of-process proxy resolver.

[commit-bot: I haz the power, 2015-02-04 07:37:53]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/892373006/1

[commit-bot: I haz the power, 2015-02-04 07:38:39]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-02-04 07:39:41]

Patchset 1 (id:??) landed as
https://crrev.com/7d4ec1aa24e79406d29e0cafbb531a3fabfe815f
Cr-Commit-Position: refs/heads/master@{#314519}

[Anand Mistry (off Chromium), 2015-02-04 07:40:00]

On 2015/02/04 07:39:41, I haz the power (commit-bot) wrote:
> Patchset 1 (id:??) landed as
> https://crrev.com/7d4ec1aa24e79406d29e0cafbb531a3fabfe815f
> Cr-Commit-Position: refs/heads/master@{#314519}

Test looks very flaky:
http://test-results.appspot.com/dashboards/flakiness_dashboard.html#testType=...

[Anand Mistry (off Chromium), 2015-02-04 07:43:35]

On 2015/02/04 07:40:00, Anand Mistry wrote:
> On 2015/02/04 07:39:41, I haz the power (commit-bot) wrote:
> > Patchset 1 (id:??) landed as
> > https://crrev.com/7d4ec1aa24e79406d29e0cafbb531a3fabfe815f
> > Cr-Commit-Position: refs/heads/master@{#314519}
> 
> Test looks very flaky:
>
http://test-results.appspot.com/dashboards/flakiness_dashboard.html#testType=...

This code isn't even linked into any target and nothing builds it.

[Noel Gordon, 2015-02-04 07:56:41]

On 2015/02/04 07:43:35, Anand Mistry wrote:
> On 2015/02/04 07:40:00, Anand Mistry wrote:
> > On 2015/02/04 07:39:41, I haz the power (commit-bot) wrote:
> > > Patchset 1 (id:??) landed as
> > > https://crrev.com/7d4ec1aa24e79406d29e0cafbb531a3fabfe815f
> > > Cr-Commit-Position: refs/heads/master@{#314519}
> > 
> > Test looks very flaky:

Ok, good thanks for looking. Could you mark the test flaky or ask the chrome
sheriff too?

Do revert the revert and I'll lgtm (back to blink).

[Anand Mistry (off Chromium), 2015-02-04 08:37:49]

A revert of this CL (patchset #1 id:1) has been created in
https://codereview.chromium.org/882173005/ by amistry@chromium.org.

The reason for reverting is: The code in this change is not linked into any
binary.

Test is flaky:
http://test-results.appspot.com/dashboards/flakiness_dashboard.html#testType=...

The likely cause of the test failure is
https://chromium.googlesource.com/chromium/src/+/bc78a2320b50eba4fe397f1f838a....
The author has been informed and the test will be fixed soon.
.