Support restricting the allowed orientations (UA wise)

- Move the UA default to a global place and use it from the app window.
- Give the UA default to the ScreenOrientationExtension ctor.
- Set the UA default as part of the JS source string.
- Enforce (according to spec) that any web facing orientation lock
  much be a subset of the UA defaults.
Merge pull request #1454 from kenchris/uadefaults

Support restricting the allowed orientations (UA wise)
[SysApps] Fixed unit test crashing

Make sure the content:: path provider is registered. We need to test
first to make sure we are not registering it twice, otherwise the second
test to register the path provider will crash.

Also add the proper dependencies on the build system.
Merge pull request #1456 from tmpsantos/sysapps_utest_fix

[SysApps] Fixed unit test crashing
[SysApps] Remove usage of XWalkRuntimeFeatures

This was the only dependency that sysapps/ had from runtime/. We keep
the usage of the XWalkRuntimeFeatures (which parses command line) in
runtime/ and add specific functions to disable each API.

The unit tests now don't refer to XWalkRuntimeFeatures. We now handle
"SysApps is disable" by not creating the SysAppsManager at all. Two
small tests were added to check if disabling the APIs individually have
some effect.

This patch is a first step to clean up the handling of extension
creation in the Android and Tizen variants. At the moment, creation of
the extensions in those ports is bypassing the SysAppsManager.
Merge pull request #1449 from cmarcelo/sysapps-not-use-xwalk-runtime-features

[SysApps] Remove usage of XWalkRuntimeFeatures
Ozone: do not call Widget::CenterWindow() when initializing the view.

If that is not done, Crosswalk's window will be 1x1 in size inside Weston.
Bump version to 4.32.67.0
[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