[Tizen] Change Sandbox IPC process title.

SetProcessTitleFromCommandLine() plays a role to change process title to
absolute path of the executable with arguments that the CommandLine object has.
For example, we want gpu process title to be "<xwalk dir>/xwalk
--type=gpu-process", not "/proc/self/exe --type=gpu-process"

However, we don't want to change browser process title, because browser process
title should be web app symbolic link path, not xwalk executable absolute path.

SandboxIPC process is the process forked by browser process. We want that
SandboxIPC process title is different from browser process title. Otherwise,
Tizen task switcher misunderstands that SandboxIPC process is also web
application process.

To achieve it,
1. Browser process must not call SetProcessTitleFromCommandLine();
2. Browser process must save argv pointer to change SandboxIPC process title later.
3. SandboxIPC process also calls SetProcessTitleFromCommandLine() to change its own process title.

BUG=https://github.com/crosswalk-project/crosswalk/issues/609
[Android] Extend android install timeout to 5 minutes for testing

For android trybots, they will use emulator to run tests.
On emulator, the operation will take really a lot of time.
[Android] When running android test, try killing adb if no devices found

It randomly happens that adb devices return empty list even device
is actually connected, killing adb and restart it can fix this.

CL=https://codereview.chromium.org/24194002
[Android] Fix the render issue introduced by single process mode.

* In Chromium, single process mode is only for Android WebView, ContentShell and
its derivatives only go to the multiple process mode.
* The context design is only for multiple process mode(ContentShell/XWalk), if we
force running it with single process mode, there are issues (black regions for
video/canvas/webgl layers, and black screen for stop/restart actions). The reason
is that Android port has browser-side compositor, and the shared context in
browser-side compositor has conflicts with renderer's contexts if running in single
process mode.
* To run ContentShell/XWalk in single process mode, we have to resolve the shared
context issue between renderer/browser.

BUG=https://github.com/crosswalk-project/crosswalk/issues/516

Conflicts:
	content/browser/renderer_host/compositor_impl_android.cc
	content/browser/renderer_host/image_transport_factory_android.cc
	content/common/gpu/client/webgraphicscontext3d_command_buffer_impl.cc
	content/common/gpu/client/webgraphicscontext3d_command_buffer_impl.h

Rework with 32.0.1700.4 code base.
Use XmbSetWMProperties to set window title for i18n issue

BUG=https://github.com/otcshare/crosswalk/issues/189
Aura: enable the touch events dispatch in DesktopRootWindowHostX11
[Tizen] Change scrollbar animator

Based on patch from: Kenneth Rohde Christiansen <kenneth.r.christiansen@intel.com>

Since we have enabled overlay scrollbars we now get the desktop behavior, which means that a thin scroll indicator is always visible, which immediately grows when scrolling and shrinks (animated) back to the small size when scrolling is over.

On Tizen we want a different behavior:
a) no scroll indicator when not scrolling
b) a think scroll indicator which is slightly offset from the right viewport edge
c) the scroll indicator should fade out (animated) when the scroll is over

This patch is changing the scrollbar animator to 'fade out' and fixes 'a)' and 'c)' from the list above.

Conflicts:
	content/renderer/gpu/render_widget_compositor.cc

Rework with 32.1700.0.4 code base.
Introduce OS_TIZEN and set specific settings for Tizen platforms

This includes disabling site themed scrollbars (we use overlay
scrollbars always), enabling double tap to zoom for zoomable pages,
disable auto playing of music (a touch is needed) as well as
moving input fields into the view when focused.

It also enables the fade out scrollbars on all Tizen platforms, not
just mobile.