Mus: Move creation of cc::Display to DisplayCompositor

Mus: Move creation of cc::Display to DisplayCompositor

What type of ContextProvider, and OutputSurface we create is a display-
compositor-specific detail and not a CompositorFrameSink specific detail.
A top-level GpuCompositorFrameSink needs a cc::Display to update the display's
surface, but it doesn't need to know how the cc::Display was set up.
This CL moves cc::Display creation to DisplayCompositor and passes in
a unique_ptr to GpuCompositorFrameSink. That way, GpuCompositorFrameSink becomes
a generic implementation that doesn't care whether an InProcessContextProvider
or some other ContextProvider was used. This will allow this code to be
reused elsewhere in Chrome.

BUG=668126
Committed: https://crrev.com/64d953d2dbde0507b1ac81ce4768911cd870366d
Cr-Commit-Position: refs/heads/master@{#436023}

[Fady Samuel, 2016-12-02 19:00:57]

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

[Fady Samuel, 2016-12-02 19:01:16]

fsamuel@chromium.org changed reviewers:
+ kylechar@chromium.org

[commit-bot: I haz the power, 2016-12-02 19:02:32]

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

[Fady Samuel, 2016-12-02 19:11:00]

PTAL! Net negative LoC! w00t!

[kylechar, 2016-12-02 19:56:18]

lgtm

[Fady Samuel, 2016-12-02 19:57:16]

The CQ bit was checked by fsamuel@chromium.org

[commit-bot: I haz the power, 2016-12-02 19:58:12]

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-12-02 21:18:42]

CQ is committing da patch.

Bot data: {"patchset_id": 20001, "attempt_start_ts": 1480708636080010,
"parent_rev": "36911e14dc25f2c48f059469a88b1841c2412fa3", "commit_rev":
"2d3919c7fdb643dd269ef39ca92f9d3631e1786d"}

[commit-bot: I haz the power, 2016-12-02 21:19:13]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-12-02 21:22:15]

Description was changed from

==========
Mus: Move creation of cc::Display to DisplayCompositor

What type of ContextProvider, and OutputSurface we create is a display-
compositor-specific detail and not a CompositorFrameSink specific detail.
A top-level GpuCompositorFrameSink needs a cc::Display to update the display's
surface, but it doesn't need to know how the cc::Display was set up.
This CL moves cc::Display creation to DisplayCompositor and passes in
a unique_ptr to GpuCompositorFrameSink. That way, GpuCompositorFrameSink becomes
a generic implementation that doesn't care whether an InProcessContextProvider
or some other ContextProvider was used. This will allow this code to be
reused elsewhere in Chrome.

BUG=668126
==========

to

==========
Mus: Move creation of cc::Display to DisplayCompositor

What type of ContextProvider, and OutputSurface we create is a display-
compositor-specific detail and not a CompositorFrameSink specific detail.
A top-level GpuCompositorFrameSink needs a cc::Display to update the display's
surface, but it doesn't need to know how the cc::Display was set up.
This CL moves cc::Display creation to DisplayCompositor and passes in
a unique_ptr to GpuCompositorFrameSink. That way, GpuCompositorFrameSink becomes
a generic implementation that doesn't care whether an InProcessContextProvider
or some other ContextProvider was used. This will allow this code to be
reused elsewhere in Chrome.

BUG=668126

Committed: https://crrev.com/64d953d2dbde0507b1ac81ce4768911cd870366d
Cr-Commit-Position: refs/heads/master@{#436023}
==========

[commit-bot: I haz the power, 2016-12-02 21:22:16]

Patchset 2 (id:??) landed as
https://crrev.com/64d953d2dbde0507b1ac81ce4768911cd870366d
Cr-Commit-Position: refs/heads/master@{#436023}