[Android] Add the test case about DomStorageEnabled and AppCacheEnabled.

Implement the test cases about DomStorageEnabled and AppCacheEnabled.

Test AppCache by setting the data in TestWebServer instance.
Test DomStorage by loading the html, in this html file, it checks
the domstorage enabled or not by javascript.

For test case "DomStorageEnabled" should add the parameter "--test_data", as follows:
build/android/run_instrumentation_tests.py --test-apk XWalkCoreTest \
--test_data xwalkview:xwalk/test/data/device_files/ \
--verbose -I --num_retries=1 -f testDomStorageEnabledWithTwoViews
[Tizen][SysApps] Add AVCodecs support in device capabilities

The main idea is as below:
1. Get supported codec and mime format list from libffmpegsumo.so
2. Use APIs in net/base/mime_util.h to verify whether a format/codec supported.
   If true, the codec will be added in the supported media codecs list.

The step 2 logic refers to implementation of
WebKit::WebMimeRegistry::supportsMediaMIMEType()

spec: http://device-capabilities.sysapps.org/
feature: https://crosswalk-project.org/jira/browse/XWALK-47
[Application][Linux] Expose interface for launch apps via D-Bus

The exported object '/running/' supports only one method in its
interface, that is used to Launch applications. The ObjectManager based
interface will come in future patches, once the notion of "running
application" is added to Crosswalk (Mikhail / Alex work).

At the moment, Crosswalk quits after the application window is closed,
even running as a service. This behavior will change in future
patches.
[Applications][D-Bus] Emit InterfacesAdded signal when app is installed

When a object is added to the bus we send all its properties (following the
ObjectManager recommendations) re-using most of the code that was added
for implementing the GetManagedObjects() call.
[Applications][D-Bus] Emit InterfacesRemoved when app is uninstalled

Even if our clients won't use this Interfaces, it may be useful for
debbuging purposes and for completeness of our implementation of
the D-Bus ObjectManager interface.

There was the need for the PropertyExporter object to export in
which interfaces it has properties.
[Android][SysApps] Support 'onxxx' event handler for display and storage

This commit fixes two things:
1. The type name in the addEventListener() should be 'attach' instead of
'onattach' according to the W3C spec. Same as 'detach', 'connect' and 'disconnect'.
2. Support 'onxxx' event handler, for example:
navigator.system.onattach = function() {...}
[Application] Rename Application class to ApplicationData

Rename Application class to ApplicationData as a first implementation step of https://docs.google.com/a/intel.com/document/d/1N0VVlut7JCWFbAEwTQc0loN9_D2JlOXRJprQeCbXY2U/edit#heading=h.23lva9lja986

That will allow us to introduce a real Application class.
Merge pull request #1206 from pozdnyakov/Rename_Application_To_ApplicationData

[Application] Rename Application class to ApplicationData
[Tizen] Fix Tizen build after r06f11403c293
Merge pull request #1236 from pozdnyakov/Fix_Tizen_build

[Tizen] Fix Tizen build after r06f11403c293
Merge pull request #1118 from qjia7/getAVCodecs

[SysApps][Tizen] Add AVCodecs support in device capabilities
Merge pull request #1225 from vcgomes/xwalk-dbus

[Applications][D-Bus] Emit InterfacesAdded and InterfacesRemoved signal
Merge pull request #1211 from cmarcelo/dbus-launch-app

[Application][Linux] Expose interface for launch apps via D-Bus
[Runtime] Register event router when launching application by app ID.

Currently the event router is not registered if we launch application by
application ID method.

This PR is to fix above issue, besides it refactors Launch() methods
inside application service.
Merge pull request #1226 from shaochangbin/app-launch

[Runtime] Register event router when launching application by app ID.
[Extensions] Remove uses of deprecated v8::String::New()

As announced in
http://permalink.gmane.org/gmane.comp.web.chromium.devel/47781, Chromium
will change to break when using deprecated V8 functions. Since the
non-deprecated versions are already available for us, we can start to
use them before we hit the breakage.

This patch changes our uses of v8::String::New() to the corresponding
new functions that take the v8::Isolate* parameter.
[Extensions] Remove uses of deprecated v8::Persistent::Dispose()/Clear()

As announced in
http://permalink.gmane.org/gmane.comp.web.chromium.devel/47781, Chromium
will change to break when using deprecated V8 functions. Since the
non-deprecated versions are already available for us, we can start to
use them before we hit the breakage.

This patch replaces the uses of Dispose()/Clear() with the
v8::Persistent::Reset() function.
[Extensions] Remove uses of deprecated v8::HandleScope::Close()

As announced in
http://permalink.gmane.org/gmane.comp.web.chromium.devel/47781, Chromium
will change to break when using deprecated V8 functions. Since the
non-deprecated versions are already available for us, we can start to
use them before we hit the breakage.

The functionality provided by v8::HandleScope::Close() is now provided
by the v8::EscapableHandleScope.
Merge pull request #1238 from cmarcelo/fix-v8-deprecated-usages

[Extensions] Fix v8 deprecated usages
Bump version to 3.32.48.0