[Android] Allow extension manager to load extension js from res/raw

This is step one of getting rid of assets for xwalk_core_library.
Because assets are not supported well for android library project.

Now XWalkExtensionManager will load extension js files from res/raw
first for internal extensions, then from assets if not found.

BUG=https://crosswalk-project.org/jira/browse/XWALK-1084
Merge pull request #1658 from wang16/pak_res_raw

[Android] Allow extension manager to load extension js from res/raw
[Runtime] Application should be terminated before uninstall or update.

The running application should be terminated when intend to uninstall or
update.

BUG=XWALK-945
FEATURE=XWALK-1060
Merge pull request #1625 from takethathe/terminate

[Runtime] Application should be terminated before uninstall or update.
Fix "XWalkExtensionsIFrameTest.IFrameUsingDocumentWriteShouldNotCrash" test failure

The "XWalkExtensionsIFrameTest.IFrameUsingDocumentWriteShouldNotCrash"
test failed on Linux due to some pending events left after
"xwalk_test_utils::NavigateToURL()". The pending events were
prosessed after the corresponding web contents had been
already destroyed causing the crash.
Merge pull request #1664 from pozdnyakov/Fix_IFrameUsingDocumentWriteShouldNotCrash

"XWalkExtensionsIFrameTest.IFrameUsingDocumentWriteShouldNotCrash" test failure
Bump version to 5.34.95.0
[Android] Fix the regression issue of http authentication on chromium 34.

Based on chromium 34, the http authentication cannot work, while
it works on chromium 32, this is because Chromium 34 starts to
support the out-of-process iframe, RenderViewHost is replaced by
RenderFrameHost, while in XwalkLoginDelegate, webcontents is still
gotten via the RenderViewHost, which causes the corresponding UI
thread for http authentication not to work. This fix resolves this
issue by replacing RenderView with RenderFrame for http authentication.

BUG=https://crosswalk-project.org/jira/browse/XWALK-1088
[Tizen][Runtime] Fix session bus issue under service mode.

Tizen 3.x and Tizen 2.x have different DBUS_SESSION_ADDRESS values.
For Tizen 2.x, DBUS_SESSION_ADDRESS points to
'/run/user/$USERNAME/dbus/user_bus_socket',
while for Tizen 3.x, DBUS_SESSION_ADDRESS points to
'/run/user/$UID/dbus/user_bus_socket'.

Since Crosswalk switches to Tizen 3.x, we need to use the latter one.

BUG=XWALK-1112
[IVI][Runtime] Fix unable to install application on Tizen IVI 3.0 image.

The package install/uninstall/update for Tizen are designed to integrate
with AMD (Application Management Daemon) on Tizen mobile 2.x, not
compatible with Tizen IVI 3.0.

This is a temporary solution to revert to use macro OS_TIZEN_MOBILE, this
means install/uninstall/update won't work with AMD on Tizen IVI. We'll
add that support back later.

BUG=XWALK-1074
Merge pull request #1661 from takethathe/ivi_bug_1074

[IVI][Runtime] Fix for installing application on Tizen IVI 3.0 image.
[Android] Packaging tool fail to run with python3.*.

1. Change the print statement to print function.
2. Add encoding when handling the file with python.
Merge pull request #1668 from shaochangbin/dbus-session-issue

[Tizen][Runtime] Fix session bus issue under service mode.
Merge pull request #1666 from ShDavidliu/update_auth

[Android] Fix the regression issue of http authentication on chromium 34...
[Runtime] Fix install issue of widget applications without 'version'
attributes.

Widget application are failed to be installed without “version="xxx”
attribute in config.xml, case is same with 'name', 'description'
elements.

Root cause of this issue is Crosswalk makes WGT follow XPK manifest checking methods.

This PR is to fix above issue.

BUG=XWALK-1108
Merge pull request #1665 from shaochangbin/tags-configxml

[Runtime] Fix install issue of widget applications without 'version' attributes.
Bump version to 5.34.96.0
Merge pull request #1670 from junmin-zhu/python3

[Android] Packaging tool fail to run with python3.*.
[Runtime] Fix launch issue for widget applications that don't have
'content' element in config.xml.

Per Widget spec, the occurrences of 'content' element can be zero or one.
If there is no 'content' in config.xml, we should still be able to launch
widget application by the default 'index.html' path

BUG=XWALK-1109
Merge pull request #1667 from shaochangbin/content-src-issue

[Runtime] Fix launch issue for widget applications that don't have 'content' element in config.xml.