[Tizen][Runtime Model] Using the xwalk logo image when icons are not given in manifest.json

The application button with default xwalk logo image will be placed on
home screen in Tizen if the icons field is not given in manifest.json.

BUG=https://crosswalk-project.org/jira/browse/XWALK-124
[Extension] Adding a Crash Extension and a crash "demo"
[Extension] Gracefully handle an ExtensionProcess crash.

This patch enables us to gracefully handle a crash from
ExtensionProcess. We use XWalkExtensionProcessHost::OnChannelError
since we can't really rely on XWalkExtensionProcessHost::OnProcessCrashed.
See a more complete explanation about this on the end of this commit message.

It is safe to rely on XWalkExtensionProcessHost::OnChannelError
since this function is called just before
BrowserChildProcessHostImpl::OnChildDisconnected gets called.
OnChildDisconnected() would, in turn, be the function that would
call our OnProcessCrashed(). For more information, please refer to
ChildProcessHostImpl::OnChannelError() from child_process_host_impl.cc.

This patch also adds the interface XWalkExtensionProcessHost::Delegate,
which now is implemented by XWalkExtensionService.
XWalkExtensionProcessHost::OnChannelError() calls then
Delegate::OnExtensionProcessDied().

For documentation reasons, I will elaborate on what happens when not
using zygote, which is the case of EP.
GetTerminationStatusImpl() from base/process/kill_posix.cc ends up
calling waitpid() with WNOHANG. If the extension process isn't ready
to reply its termination status by then, we won't block while waiting
for it and that function will return TERMINATION_STATUS_STILL_RUNNING
to BrowserChildProcessHostImpl::OnChildDisconnected(). When that happens,
OnProcessCrashed() ends up never being called. That is not the case
for OnChannelError(), thus we use that as our hook.
Using zygote would put the necessary infra-structure in place,
but it would also bring more than what we currently need.
[Runtime] Fix RuntimeContext ownership and unify its creation

On Android RuntimeContext used to be a singleton which is wrong as content::ContentBrowserClient lifetime should be equal to the duration of the browser session, meaning its creation&deletion should be controlled by BrowserMainLoop.

This patch unifies the creation of RuntimeContext between android and others removing ugly '#ifdefs' and unneeded difference in the code path.
Merge pull request #1123 from jeez/crash-handling

[Extensions] Handle ExtensionProcess crashes gracefully
Merge pull request #1142 from cmarcelo/xwalk-dbus

[DBus] Add PropertyExporter and DBusManager classes
Bump version to 3.32.40.0
[Android] Fix the failed test case about testPauseAndResume.

Due to the rebase to v32, the function "onActivityPause" and
"onActivityResume" was deleted from ContentViewCore.java.

The fix is to implement the onPause and onResume by another
function interfaces.

BUG=https://crosswalk-project.org/jira/browse/XWALK-351
[Tizen] add the 'gst-plugins-atomisp-devel' buildrequires to spec

chromium needs the header and lib files exported from this package to drive the
camera device on Tizen 2.1 hardware platforms.

BUG=XWALK-176
[Android] Correct activity name in core shell debug script

It's not synced with the activity name in
runtime/android/core_shell/AndroidManifest.xml
[WiDi API] Destroy XWalkView instance when presentation content is closed
The XWalkView instance should be destroyed once the presentation content is closed.
Otherwise, the resources allocated would be leaked. For example, zombie pages would
be listed in chrome web inspector (chrome://inspect) after the presentation content gets
closed by calling window.close API.

BUG=https://crosswalk-project.org/jira/browse/XWALK-336
[Android] Fix ActionUri test failure after rebase to M32

It's caused by the changing of RequestBeginning api in
content::ResourceDispatcherHostDelegate.

Fix by adjusting the api in xwalk's delegate accordingly.
Merge pull request #1140 from takethathe/icon

[Tizen][Runtime Model] Using the xwalk logo image when icons are not given in manifest.json
[Runtime Model] Add permissions handler for manifest.json

Permissions handler can parse the permissions field in manifest.json,
and save the permissions information into Application object as
ManifestData struct.
Merge pull request #1089 from takethathe/permissions_handler

[Runtime Model] Add permissions handler for manifest.json
[Android] packaging tool fails to run on Windows host.

It's because the ant on Windows would crunch the following flags
when the current flag is set with null, which would cause the
packaging stage failed. This is only a issue on Windows host.
Fix it with setting the flag with white space.
Merge pull request #1138 from jchen10/camera

[Tizen] add the 'gst-plugins-atomisp-devel' buildrequires to spec
[Runtime] Add runtime model event core classes

There are two event types for runtime model which are different from ordinary
DOM events(see http://www.w3.org/2012/sysapps/app-lifecycle): application
events which are events send to application indicate what’s happening to the
application, like launch, terminate, suspend and etc; system events which are
events sent by the system, a system event can wake up a terminated application.
This patch introduces some core classes to register and handling such events.

Implementation details:
EventObserver is a base class for observing runtime model events.

ApplicationEventRouter is a per application class dispatching events sending to
the application. It will be created when an application is loaded. It also
provides system events support.

ApplicationEventManager is the service class managing all application event
routers.
[Runtime] Add application event router unittest
Merge pull request #1057 from seanlong/event_router

[Runtime] Add runtime model event core classes