Fix leak of DictionaryValue in ApplicationStorageImpl::GetInstalledApplications()

Use scoped_ptr for DictionaryValue returned by Deserialize() to
prevent a memory leak.
Roll chromium-crosswalk to 5a02711.

[Tizen][GPU][Perf] Prevent GPU scheduler from thrashiing.
Merge pull request #1472 from ds-hwang/gpubug

Roll chromium-crosswalk to 5a02711.
Merge pull request #1466 from nagineni/memory_leak

Fix leak of DictionaryValue in ApplicationStorageImpl::GetInstalledApplications()
Add Thiago Santos to extensions/OWNERS
ApplicationProtocolHandler supports multi apps

This is a step in enabling of Shared process model.
ApplicationProtocolHandler is given with ApplicationService instance and the corresponding application instance
is fetched from the service via newly added "GetApplicationByID" method.
Merge pull request #1473 from cmarcelo/extension-owners

Add Thiago Santos to extensions/OWNERS
[Extensions] Make extension namespace read-only

Extensions export their JS content under their namespace,
which is created with the extension name. That means an
extension called "xwalk.sample" will export its functions
below the "xwalk.sample" object in JS.
This patch avoids that one do things like "xwalk.sample = null",
by marking the extension namespace object as read-only whenever
an extension's code was loaded. Trying to do it, however, won't
raise any exceptions. That follows how Javascript behaves for a
snippet like:

<script>
// Returns the window object with "foo3" added to it.
Object.defineProperty(window, "foo3", {configurable: false, writable: false, value: "foooo"});

// Returns null. No exceptions are raised.
window.foo3 = null;

// Returns "foooo".
window.foo3;
</script>

We don't touch entry_points (changing their properties to read-only)
because this is something the extension writer should do him/herself
when writing the JS shim, by JS means, since we can't predict
which entry_points should be marked as read-only or not.
In other words, that is part of the extension API being implemented.

BUG=https://crosswalk-project.org/jira/browse/XWALK-605
BUG=https://crosswalk-project.org/jira/browse/XWALK-600
TEST=./out/Release/xwalk_extensions_browsertest --gtest_filter="NamespaceReadOnlyExtensionTest.*"
TEST= Also covered by TCT in the "_in_tizen" tests.
Merge pull request #1475 from jeez/extension-read-only

[Extensions] Make extension namespace read-only
Merge pull request #1426 from pozdnyakov/ApplicationProtocolHandler_supports_multi_apps

ApplicationProtocolHandler supports multi apps
Remove "Runtime" and "Dialog" extensions

Runtime extension was added as a test for our internal extension
infrastructure and is not being used neither by Android or Tizen. There
are other extensions that test this infra, so it's OK to remove.

Dialog was an experimental extension added when Crosswalk started that
served as example. When we changed to Aura backend in Linux, it stopped
working. Given that is unmaintained we are better off removing it.
Implement the screen.orientation property

This adds the property and it is ensured to be correct after
the first orientation change. Another patch will make sure it is
100% correct in all cases.
Merge pull request #1476 from kenchris/orientationprop

Implement the screen.orientation property
[Extensions] "Fix" and enable test MultipleEntryPointsExtension.MultipleEntryPoints

This test was added by commit 77bcab7bd3ba998196da6958c590af9fe32a1cd7
"[Extensions] Add tests for loading extension with multiple entry points", but
it was never enabled.

Later then, commit 76dbc259ef6e58c1667f763403201c50d4803bc5 "[Extensions] Reduce
boilerplate for external extension tests" mispelled the path for the
multiple_entry_points_extension.so.

This patch fixes this and enables this test.
Merge pull request #1474 from cmarcelo/remove-dialog-runtime-extensions

Remove "Runtime" and "Dialog" extensions
Merge pull request #1477 from jeez/entry_points-fix-test

[Extensions] "Fix" and enable test MultipleEntryPointsExtension.Multiple...
[Extensions] Add a setter callback accessor to trampolines

Prior to this patch we weren't supporting trampolines with setter
callbacks. This patch enables extensions so can implement an API
to be used like:

"window.onFooChanged = function() { foo("teste"); };"

and use window.onFooChanged as an entry point to an extension called
xwalk.sample, for instance.

BUG=https://crosswalk-project.org/jira/browse/XWALK-835
TEST=./out/Release/xwalk_extensions_browsertest --gtest_filter="MultipleEntryPointsExtension.*"
Merge pull request #1479 from jeez/lazy-load-setter-callback

[Extensions] Add a setter callback accessor to trampolines
[Android] Load manifest.json if it exists but not specified in options.

Because the manifest has been supported by packaging tool, and it's the
recommended source for packaging. So manifest.json will be loaded
if it does exist.