DEPS.xwalk: chromium-crosswalk roll - 0112237..f344a2f

f344a2f Merge pull request #104 from rakuco/ozone-egl-changes-for-wayland
66c2cfd [Temp] Add EGL-specific changes for Wayland.
db349fa Merge pull request #103 from rakuco/ozone-component-build
5183bb4 [Temp] Export GpuProcessHost::AddFilter().
adce827 [Temp] Backport Chromium r233274 to M32.
Merge pull request #1453 from rakuco/cr-roll

DEPS.xwalk: chromium-crosswalk roll - 0112237..f344a2f
DEPS.xwalk: Track ozone-wayland.git.

This is a very important part of the process, as the code expects ozone/ to
be in src/.
Add Ozone-Wayland support
[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 is being tracked upstream by http://crbug.com/266310