[SysApps] Simplification of how to init the PathServices

As suggested by Babu, there is a much easier way to start the
PathService specifically for testing.
Merge pull request #1457 from tmpsantos/media_init

[SysApps] Simplification of how to init the PathServices
Merge pull request #1455 from rakuco/ozone-wayland

Add support for Wayland to Crosswalk.
[Packaging] Pass --no-keep-memory to ld by default.

When building Crosswalk (Chromium, in fact) on an IVI chroot, ld ends up
running out of memory.

Work around the issue by passing --no-keep-memory to ld so that it optimizes
for memory consumption over speed. I have not noticed any significant drop
in speed, though.

Do not add any checks for IVI as it does not hurt to have this on all
profiles.
[Packaging] Be compatible with multiple Tizen versions and profiles.

Prepare for the future and start detecting features and versions so that we
can support other Tizen versions and profiles besides Tizen 2.1 Mobile.

Checking for specific profiles is not very future-proof. We therefore try to
look for either specific features that may be enabled in the current profile
(such as Wayland support) or for a certain Tizen major version (the
differences betwen Tizen 2 and Tizen 3 are big enough that we need different
patches and build dependencies, for example).
[Packaging] Add a Mesa patch for Wayland when building for Tizen.

Import a patch from the Ozone-Wayland repository to prevent crashes when
using Mesa and Ozone caused by the way Chromium has GL headers in both
third_party/khronos and third_party/mesa and the wrong ones (with wrong
pointer sizes) may be picked up.

This patch should actually be used by anyone testing Chromium on Wayland,
but this would require us to have a Chromium Mesa fork of our own. For now,
then, we're going to apply it automatically only for Tizen and try to solve
the issue upstream. It is tracked by http://crbug.com/266310
Merge pull request #1459 from rakuco/tizen-ivi-support

[Packaging] Add all necessary spec file changes to support Tizen IVI.
Bump version to 4.32.68.0
[Android] Fix the crash issue of loading app from app:// scheme.

The fixed places:
1. As the resource rquest URL was canonicalized to lowercase in
runtime core, the host name exacted from the URL may be inconsitent
with the app package name, if there is capital letter in the package
name. So convert package name to lowercase before comparing these
two strings.
2. The unpermitted resource request should not be processed. Once
such request is received, the request job should be marked as done,
and should returned from the process function at once. So add the
missing return to the related place.

BUG=https://crosswalk-project.org/jira/browse/XWALK-808
Merge pull request #1458 from gaochun/bug808

[Android] Fix the crash issue of loading app from app:// scheme
Merge pull request #1444 from junmin-zhu/toolpath

[Android] Add "--tool-path" option for make_apk_test.
Merge pull request #1398 from zhang-qing/master

Add myself to the AUTHORS file.
[Android] Support back key to exit fullscreen

Previously, there is no way to exit fullscreen if developer
doesn't provide one. And back key is used to navigate backward.

Move the handling of back key into xwalk core and try to exit
fullscreen prior to navigate backward.
[Android] Fix crash issue in Android extension system

On Android, the extension objects and instances are deleted explicitly
by JNI invokation from Java side. However, both extension objects and
instances are designed to be owned by XWalkExtensionServer, it means
that only XWalkExtensionServer is allowed to delete them, otherwise a
pointer would be deleted twice and cause crash issue.

This fix is to address the above issue and make sure the extension
objects and instances are owned by XWalkExtensionServer. Moreover, the
extension objects on native side will be alive in the whole process
lifecycle and reused by Java-side if resuming back.

BUG=https://crosswalk-project.org/jira/browse/XWALK-821
Merge pull request #1446 from wang16/fullscreen_html5

[Android] Enable W3C fullscreen API support
Add screen.onorientationchange event listener

The function set is fired whenever the orientation changes.
The test has been updated to count how many times the orientation
has changed so far.

The entries have been changed as there are some unresolved bugs
with the ondemand loading making this not work otherwise.
Merge pull request #1460 from kenchris/onorientation

Add screen.onorientationchange event listener
Bump version to 4.32.69.0
Merge pull request #1451 from ShDavidliu/RunningFromSD

[Android] Implement the functions of application working from SD-Card.
[Android] Add adb_gdb_xwalk_runtime_client_embedded_shell for extension debugging

Xwalk extension is not attched to xwalk_core_shell, we needed to run xwalk_runtime_client_embedded_shell
to debug extension.