Have the component build use the same manifest tricks for the installer archive that are now used by chrome_elf.dll on trunk.

This means:
1) chrome.exe.manifest remains the same
2) Component DLLs are now the only special cased DLLs (instead of *.dll) -- this avoids allowing official DLLs to somehow load in the component build for someone that made a change that would otherwise break their load in an official build.
2) {version}.manifest is augmented with all the component DLLs.
3) Component DLLs are also copied in the Installer/ folder for setup.exe to work as well (without having to use the old setup.exe.config\probing\privatePath technique which isn't XP compatible).

I'd like to get a better solution up for (3), but since this is currently breaking developers I'll get this fix in now and we can iterate after.

TBR=grt
NOTRY=True
BUG=318950
TEST=Install a component build of Chrome, verify that chrome.exe and setup.exe run properly.

Review URL: https://codereview.chromium.org/63153013

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@235244 0039d316-1c4b-4281-b951-d872f2087c98
linux aura: Fix window activation in some X11 window managers.

Some X11 window managers do not support extended window manager hints (EWMH) like
_NET_ACTIVE_WINDOW. In such cases, instead of trying to set the _NET_ACTIVE_WINDOW
atom on the X11 RootWindow, use XRaiseWindow() to activate a window.

BUG=317856
R=erg@chromium.org

Review URL: https://codereview.chromium.org/68063003

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@235245 0039d316-1c4b-4281-b951-d872f2087c98
SVN changes up to revision 235244
SVN changes up to revision 235245