[Tizen] Add element namespace recognition in app-widget manifest handler

This patch adds code testing whether app-widget element and its children
are in tizen namespace.
[Tizen] Prevent unpacked widget installation

With this patch installer aborts installation when a path
to a widget points to a directory.

BUG=XWALK-2927
Bump version to 11.39.248.0
Merge pull request #2627 from KFilipek/XWALK-2927

[Tizen] Prevent unpacked widget installation
Merge pull request #2626 from tweglarski/AppWidgetNamespaceFix

[Tizen] Add element namespace recognition in app-widget manifest handler
Bump version to 11.39.249.0
[Tizen] Parsing of app-control entry in widget manifest

In xml manifest, we have following structure of app-control entry:
<tizen:app-control>
    <tizen:src name="edit.html"/>
    <tizen:operation name="http://tizen.org/appcontrol/operation/edit"/>
    <tizen:mime name="image/jpg" />
    <tizen:uri name=""/>
</tizen:app-control>

Information about app-control should be passed to platform's manifest.xml
during installation of widget.

This information enables launching applications based on app control as
handler for given URI or MIME type.
Merge pull request #2592 from tiwanek/XWALK-1490

[Tizen] Parsing of app-control entry in widget manifest
[Tizen] Tune up app-widget element parsing in its manifest handler

Tizen 2.2 WRT Core Spec:
 - does not classify as invalid, widgets with:
   - more than one primary app-widgets,
   - no primary app-widget,
 - does specify that box-icon element is optional.

This patch removes unnecessary validation of primary attribute
in app-widget element and fixes parsing of box-icon element.

Link to the spec:
https://source.tizen.org/sites/default/files/page/tizen-2.2-wrt-core-spec.pdf
Merge pull request #2634 from tweglarski/AppWidgetTuneUp

[Tizen] Tune up app-widget element parsing in its manifest handler
Bump version to 11.39.250.0
[Tizen] Add explicit dependencies on some targets.

This fixes some issues with a component=shared_library build that just
made it evident that we were using code from some parts of Chromium
without depending on the targets:

* application/browser/application_tizen.cc uses ui::PlatformEventSource.
* runtime/browser/ui/splash_screen_tizen.cc uses
  ui::ImplicitAnimationObserver.
Merge pull request #2638 from rakuco/tizen-add-target-dependencies

[Tizen] Add explicit dependencies on some targets.
Bump version to 11.39.251.0
[Tizen] Fix multiple occurrences of author in widget setting.
According to widget spec(http://www.w3.org/TR/widgets/#the-author-element-and-its-attributes), the author element's occurrences should be zero or one.
If there are more than single occurrences, just read the first one and ignore others.

BUG=XWALK-2986
Merge pull request #2640 from yejingfu/fix-widget

[Tizen] Fix multiple occurrences of author in widget setting.
Global 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.