3rd part of porting Chrome Ash to Windows 7

3rd part of porting Chrome Ash to Windows 7

This is the Chrome side that
1- removes windows 8 specific checks
2- disconnects the fake window_tree_host_win
3- connects the remote_window_tree_host_win

With this change you can now see the ash desktop but not interact with
it since input events have not been enabled.

Here is the second part
https://codereview.chromium.org/211863003/

First part with rationale:
https://codereview.chromium.org/199843004/

Note: this is a redo & rebase of
https://codereview.chromium.org/227573007/


BUG=356475
TEST=none
patch from issue 235683005

BUG=

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=264680

[sky, 2014-04-14 20:30:06]

Meta question. If we want to run this on the desktop, why bother using the
remote host at all? We can run everything in process, right?

[ananta, 2014-04-17 20:48:14]

On 2014/04/14 20:30:06, sky wrote:
> Meta question. If we want to run this on the desktop, why bother using the
> remote host at all? We can run everything in process, right?

I hope cpu's email response clarified the reason we are doing this. I updated
this CL with fixes
for ash_unittests failures on Win7. Mostly around not supporting multiple
displays on Windows and
host resize on the same lines as Win8.

PTAL

[sky, 2014-04-17 22:02:59]

I still have concerns about this approach and was hoping to talk with cpu when
he gets back. Until then though, LGTM

[ananta, 2014-04-17 23:15:58]

The CQ bit was checked by ananta@chromium.org

[commit-bot: I haz the power, 2014-04-17 23:17:23]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/ananta@chromium.org/235933004/20001

[commit-bot: I haz the power, 2014-04-18 00:05:01]

Change committed as 264680