[Android] Clean java compiling warnings in client and webchrome client tests

The warnings are for java reflection definition.
Use Class<?> instead of Class to declare Class type to resolve these issues.

BUG=https://crosswalk-project.org/jira/browse/XWALK-771
[Tizen] Install support files for "run as service" mode

This commit adds to the installation the support files for D-Bus and
systemd to make Crosswalk auto activated by D-Bus and managed by
systemd (in the user session). The xwalkctl and xwalk-launcher
applications should be used to interact with service mode.

Crosswalk is installed as a systemd user service, named
xwalk.service. To check it's status, you can use (always with app user
on Tizen 2.x)

    $ whoami
    app

    [ Because shell via sdb doesn't set the right D-Bus session address,
      we need to set it manually because systemctl uses it. Our xwalk
      tools on Tizen will automatically find the right address. ]

    $ export DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/app/dbus/user_bus_socket
    $ systemctl --user status xwalk.service

Other regular systemd commands (restart, stop, start) should work as
well. Because of D-Bus auto activation feature, Crosswalk doesn't need
to be manually started. Just invoke xwalkctl or xwalk-launcher, and
Crosswalk will be started behind the scenes.

In service mode, the logs of Crosswalk go to systemd's "journal". You
can check that by using (as root, at the moment)

    [ Trick to show more information ]

    # export COLUMNS=1000
    # systemd-journalctl _COMM=xwalk

For debugging it might be useful to directly run Crosswalk (to use gdb
or other tools), in that case, stop the current running Crosswalk using
'systemctl --user stop xwalk.service' and run xwalk binary directly
passing '--run-as-service'.

For now, we still support the current (non-service) way of using
Crosswalk. To avoid conflicts in the configuration files, we use a
different data directory (in $HOME). This means that we have different
app database, so do not expect apps installed in one way to work in
another.

Once we make sure service mode is running OK, we plan to remove the
current way of using Crosswalk (at least on Tizen)

- remove the "xwalk --install and --uninstall" switches;
- remove the "xwalk" script from $PATH;
- and then make the service mode default.

What is still missing in service mode is support for the Tizen-specific
steps of the installation (making the installed app appear on the
homescreen) and tighter integration with Tizen task switcher. Those will
come in following patches.
Revert "Fix compilation error with -Werror=delete-non-virtual-dtor flag set"

It turns out my checkout was probably outdated at the time I got this
warning, as GCC 4.8 does not complain about this anymore.

This reverts commit 01c4780c6ecd9901f965ded475e8f9b638738921.

Conflicts:
	runtime/browser/xwalk_browser_main_parts.cc
Merge pull request #1427 from pozdnyakov/Disable_NoCSP

Disable NoCSP unit test
Merge pull request #1425 from rakuco/revert-unneeded-gcc48-fix

Revert "Fix compilation error with -Werror=delete-non-virtual-dtor flag set"
Merge pull request #1412 from cmarcelo/run-as-service

[Tizen] Install support files for "run as service" mode
[Application] Fix build warning - unused variable

This object don't need a variable
Merge pull request #1429 from ricardotk/minor-fix

[Application] Fix build warning - unused variable
Bump version to 4.32.63.0
Merge pull request #1416 from ShDavidliu/java_reflect

[Android] Clean java compiling warnings in client and webchrome client tests.
[Android] Enable multiple threads for rasterization

On Android, since impl side painting is enabled as default, the
rasterization is scheduled to a seperate threads. However, the default
number of threads for rasterization is 1.

This commit is to calculate the appropriate number of raster threads
according to the number of CPU cores. It could take advantage of the
multi-core hardware capability and bring performance boost in
rasterizing, according to the result of some experiments.
Merge pull request #1434 from hmin/raster-thread-num

[Android] Enable multiple threads for rasterization
[do not merge][application] Use Application for external URLs.

Use Application for external URLs. Rationals:
1) allows web pages to use some of XWalk APIs
2) makes in-browser testing simpler: no need in APIs like "Rungtime::SetGlobalObserverForTesting"
3) External URLs and applications share the same code path, which is better for both testing and maintainance

The  "app.launch.web_url" manifest key is used as application entry point for external URLs loading.

WIP: in-browser tests should be updated accordingly.