Update application_service.cc

I suppose this place should be 'false' because actually the Installation is 'failed' due to 'it's already installed', isn't it?
[Extensions] Use ContainsKey() from base/stl_util.h

Containskey() is exactly what this code needed. We keep using
find() (and the comparison to end()) when we will later make use of the
iterator.
[WiDi API] Implement navigator.presentation.requestShow API on Android

This patch is to implement navigator.presentation.requestShow for
showing a new HTML page on the secondary display.

IMPLEMENTATION NOTES:
o Web messaging can be used for communication between the opener window
  and presentation window.
o Only one presentation is allowed to be created. If there is already a
  presentation showing, an attempt to call requestShow will fail.
o A presentation will be dismissed in case of:
  1. window.close is called to close the presentation DOM window, or
  2. The presentation display is disconnected, and there is no available
     display for presentation show any more.
o The DOM window object for presentation is retrieved from the routing id
  of RenderView. It follows the way chrome.app.window.create does.

TODOS:
o Add `destroy` into XWalkView to destroy an XWalkView instance.
o Add `Promise` support for requestShow API instead of using callback.
o Make it backward-compatible on Android

SPEC=http://otcshare.github.io/presentation-spec/index.html
BUG=https://github.com/crosswalk-project/crosswalk/issues/577
[Runtime] Add Manifest keys handler mechanism

The key handler can parse specific member in manifest.json for more
information, and save these information into the Application object, by
this, it will be easier to use without parsing these information every
time. The mechanism also can treat dependence relationship between
Manifest keys, it make sure that a high priority key will be always
parsed before a low one, means that when parsing the low priority key,
all required information has been prepared yet.

The key handler also can validate if the key value is allowed for this
application.
Revert "[Tizen] Enforce device scale factor value to '2.0' on Tizen"

This reverts commit c79b41fde47fe0a6da116c9d4f0c2e9ad5410e15.

As Aura scales all the contents including UI elements, this change affected status bar appearance. The status bar should handle HIDPI properly before we can enable it again on Tizen.
Merge pull request #1064 from cmarcelo/contains-key

[Extensions] Use ContainsKey() from base/stl_util.h
Bump Crosswalk to version 3.
Merge pull request #1066 from pozdnyakov/Revert_Scale_Factor

[Tizen] Revert "[Tizen] Enforce device scale factor value to '2.0' on Tizen"
Merge pull request #1068 from jeez/xwalk-3

Bump Crosswalk to version 3.
[SysApps] Add the convenience classes and prototypes

These C++ classes and JavaScript prototypes are helpers for the common
places that appear all around the SysApps APIs specifications.

The main features are:

- Helpers for creating objects managed by the extension.
- Easy way of declaring API methods.
- EventTarget implementation, and thus, helpers for dealing with
  events.

For more information, check the documentation on the code.
[SysApps] Add unit tests for the convinience classes
[SysApps] Add browser tests for the common JavaScript API

These tests are testing the functionality of the helper JavaScript
prototypes and objects, like the EventTarget.
[UI] Clean NativeAppWindowViews

Remove unnecessary forward declarations, includes and ifdefs. Now that
Windows is using Aura, all the platforms using Views system (Win, Linux
and Tizen) are using Aura, so no more ifdef guards for USE_AURA.
Merge pull request #1069 from cmarcelo/clean-native-app-window-views

[UI] Clean NativeAppWindowViews
[Extensions] Check for conflicting entry points in the ModuleSystem

As we may have extensions coming from various processes, think that internal
extensions are run in the Browser Process and external extensions are run in
the Extension Process, the only point when we have all information of all the
extensions that would be run for a context is the module system.

So, if conflicting entry points are found, we log this as an warning and do
not register the extension.
Bump version to 3.31.31.0
[Runtime Model] Implement non-persistent main document.

The following CL is to implement
https://crosswalk-project.org/jira/browse/XWALK-2.

The CL makes ApplicationProcessManager as an Observer for Runtime
objects. Therefore, whenever a Runtime object/Window is added or
removed, the ApplicationProcessManager could be notified.
Merge pull request #1007 from wuhengzhi/remotedebug

[Android] Add the test case about enableRemoteDebugging.
Merge pull request #1043 from hmin/widi-android-part2

[WiDi API] Implement navigator.presentation.requestShow API on Android
[Runtime] Add application test API and adjust API browser test

An internal extension for application API test is created to explicitly return
the API test result. For example, with this API we don't to need wait and test
the page title or Runtime count anymore, a call to xwalk.app.test.notifyPass()
or xwalk.app.test.notifyFail() will return the test result to runtime process.

The application API browser test will register this extension in setup phase.
And block wait for the test complete.