Revert of Move content:: scheme registrations from chrome/ to content/.

Revert of Move content:: scheme registrations from chrome/ to content/. (patchset #1 id:1 of https://codereview.chromium.org/1137103003/)

Reason for revert:
Breaks some layout tests

BUG=489672
Original issue's description:
> Move content:: scheme registrations from chrome/ to content/.
>
> Both 'chrome:' and 'chrome-devtools:' are content-level schemes; we
> should do their various renderer-side scheme registrations in content
> (RenderThreadImpl::RegisterSchemes) rather than in chrome
> (ChromeContentRendererClient::RenderThreadStarted).
>
> R=jochen@chromium.org
>
> Committed: https://crrev.com/dcd7aad11d33ffd6dffe440ce32a0228c0843a67
> Cr-Commit-Position: refs/heads/master@{#330506}

TBR=jochen@chromium.org,philipj@opera.com,sofbjornf@opera.com,mkwst@chromium.org
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true

Committed: https://crrev.com/b2ecf6a9a13aebad7b529ef5a39aa291f6542560
Cr-Commit-Position: refs/heads/master@{#330513}

[hiroshige, 2015-05-19 13:22:33]

Created Revert of Move content:: scheme registrations from chrome/ to content/.

[commit-bot: I haz the power, 2015-05-19 13:22:51]

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

[commit-bot: I haz the power, 2015-05-19 13:23:25]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-05-19 13:24:17]

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

[Mike West, 2015-05-19 14:03:25]

On 2015/05/19 at 13:24:17, commit-bot wrote:
> Patchset 1 (id:??) landed as
https://crrev.com/b2ecf6a9a13aebad7b529ef5a39aa291f6542560
> Cr-Commit-Position: refs/heads/master@{#330513}

LGTM, thanks for the revert.

It's strange, though. This CL just moves the registration; it was in the
existing code already (line 499 of
chrome/renderer/chrome_content_renderer_client.cc). Why wasn't it showing up
already? And why aren't chrome-extension and chrome-extension-resource showing
up?

[Mike West, 2015-05-19 14:05:55]

On 2015/05/19 at 14:03:25, Mike West (holiday in DE) wrote:
> On 2015/05/19 at 13:24:17, commit-bot wrote:
> > Patchset 1 (id:??) landed as
https://crrev.com/b2ecf6a9a13aebad7b529ef5a39aa291f6542560
> > Cr-Commit-Position: refs/heads/master@{#330513}
> 
> LGTM, thanks for the revert.
> 
> It's strange, though. This CL just moves the registration; it was in the
existing code already (line 499 of
chrome/renderer/chrome_content_renderer_client.cc). Why wasn't it showing up
already? And why aren't chrome-extension and chrome-extension-resource showing
up?

Oh. Of course. Because the registrations were in `chrome/`, and DumpRenderTree
only know about `content/`. :/

[Mike West, 2015-05-19 19:07:52]

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

The reason for reverting is: Fixing the layout tests:

Patch 1: https://codereview.chromium.org/1143593006
Patch 2: [This patch]
Patch 3: https://codereview.chromium.org/1139053004/.