[Tizen] Move application binary path from .config to  TZ_USER_APP / TZ_SYS_RW_APP

user application binary is now located in TZ_USER_APP instead of /$HOME/.config
global application binary in TZ_SYS_RW_APP instead of /usr/apps/.config

BUG=XWALK-2672

Signed-off-by: Sabera Djelti (sdi2) <sabera.djelti@open.eurogiciel.org>
[Tizen] XWalkExtension class refactoring

A type of a field in XWalkExtension class was changed
from base::ListValue to std::vector<std::string>
to avoid unnecessary conversions.
Fix unit tests in id_util_unittest.cc file

This path adds prefix 'xwalk.' at the beginning
of tested application ids for Tizen platform.
Tests fixed:
- IDUtilTest.GenerateID
- IDUtilTest.IsValidApplicationID
[Tizen] Xwalkctl should list xpk apps as well

This patch fixes listing of installed xpk apps by xwalkctl.

BUG=XWALK-3004
[Tizen] Fix calculation for display rotation angle.

For landscape devices which have landscape-primary as default orientation, the rotation calculation " ((rot - 1) % 4) " gets invalid value that might cause unexpected result, for example when converting from portrait-primary to landscape-primary, the "rot" should be 3 (ROTATE_270) rather than -1 (invalid value).
This CL is to correct the rotation calculation.
[Android] Fix the access issues from iframe.

This patch is to fix the cross origin issues when access the different
origin urls in iframe.
The instance of XWalkSettings was not initialized when the preference
value was got, so can not set the value to XWalkSettings.
Adjust the code to generate the instance of XWalkSettings before load
the preference value.

BUG=XWALK-2685, XWALK-2905
Merge pull request #2550 from eurogiciel-oss/multiuser

[Tizen] Move application binary path from .config to  TZ_USER_APP / TZ_SYS_RW_APP
Merge pull request #2656 from yejingfu/bug-fix

[Tizen] Fix calculation for display rotation angle.
Merge pull request #2641 from tiwanek/XWALK-3004

[Tizen] Xwalkctl should list xpk apps as well
Ignore style errors about override vs OVERRIDE

See https://groups.google.com/a/chromium.org/forum/#!msg/chromium-dev/EW0wSDQQK8I/H0gsPtDtRmAJ
Merge pull request #2658 from pozdnyakov/ignore_override_style_errors

Ignore style errors about override vs OVERRIDE
Merge pull request #2633 from aszafranek/IDUtilTestFix

Fix unit tests in id_util_unittest.cc file
Merge pull request #2635 from sstolinski/sstolinski

[Tizen] XWalkExtension class refactoring
Merge pull request #2657 from wuhengzhi/xwalk_2685_2905_iframe_access_issue

[Android] Fix the access issues from iframe.
The xwalk::Runtime class (and related code) refactoring

The major changes (improvements):
- The Runtime class now only handles WebContents, it's unaware of the UI.
- The Runtime UI logic is encapsulated within the RuntimeUIDelegate implementation.
- Runtime life-cycle is definite - it is owned by the observer instead of being a suicide.
- Runtime::Close() causes the wrapped content::WebContents::Close() which had not happen(!) before.
- Multiple code clean-ups and simplification.
Improve manifest handlers unit test utilities

This patch introduces functions creating default configuration
data for both manifest types (TYPE_MANIFEST and TYPE_WIDGET).
Merge pull request #2630 from pozdnyakov/runtime_refactoring

 The xwalk::Runtime class (and related code) refactoring
runtime: Add aura-only native support

This CL brings aura-only native support for the browser runtime, where views
toolkit dependency is opt out. This is particularly useful for embedded and
limited systems, where the runtime is used always as a fullscreen application
to the host window system. This is aimed to work with Ozone DRI or GBM
implementations.

Testing was performed on Ubuntu Linux 14.04 platform.

TEST= $ python xwalk/gyp_xwalk -Dchromeos=0 -Duse_ozone=1 -Dembedded=1 -Duse_udev=1 -Dozone_platform_gbm=1 -Dozone_platform_wayland=0 -Ddisable_nacl=1
      $ ninja -j16 -C out/Release xwalk
      $ ./out/Release/xwalk --ozone-platform=gbm http://hexgl.bkcore.com/play/
runtime: Add cmd line option for changing native host window bounds

Ideally we would like to use ui::DisplayConfigurator for hotplug the monitors
and set the host window bounds automatically based on their mode sizes. That's
not possible though cause Crosswalk embedded solution doesn't fetch ChromeOS
dependencies, which is where ui::DisplayConfigurator situates.

Our solution here therefore is to pass through command-line options the native
bounds, using --xwalk-host-window-bounds=800,600 (or whatever is the
appropriated monitor resolution). One would also just link this newly option
with sysfs output like --xwalk-host-window-bounds=`cat /sys/class/graphics/fb0/virtual_size`
Bump version to 11.39.254.0