Bump version to 0.9
[NetworkBearer] Use anonymous namespace instead of static functions

Get rid of some C-isms and follow the coding style.
[NetworkBearer] Implement the "request route" functionality

This is wrong, but it is exactly what the Tizen runtime is doing, so
it was kept for compatibility.

- Routes should not be programmatically defined by the app, it has
  a strong chance of messing with the environment as a whole.
- Allowing apps to do this is probably not safe.
- We add a route just for a single IP, but a hostname might resolve
  to several IPs.
[NetworkBearer] Implement the "release route" functionality

Tizen runtime implements the "release route" by simply
disconnecting the network interface. We are doing the same here for
compatibility, but it is obviously wrong.
[Bookmark] Add BookmarkProvider

This BookmarkProvider provides the native bookmark operations.

35/36 of the tct tests are passing. We can assume that is 100%, because
the only test not passing is related to tizen.bookmark being read-only.
This object is created by Crosswalk extension system, and fix will be
done there.
[Time] Use new C++ wrapper in common/
[SystemSetting] Use new C++ wrapper in common/
[Bookmark] Fix coding style
Fix compilation for Desktop

Bookmark is implemented for Mobile only and the function access() is
defined in unistd.h.
[SystemInfo] Decouple SystemInfoContext with the multiple system info sub classes
Add XW_Extension_EntryPoints.h

This defines an internal interface in Crosswalk to setup "entry points"
of the API, so that Crosswalk can load the JS API on demand.

For example, 'tizen.time' will be loaded when the web content tries to
access 'tizen.time' in JS, but also when the web content tries to access
'tizen.TZDate'. This extra symbols are the entry points.
Add entry point information for extensions using new C++ wrapper

Entry point information is used by Crosswalk to know what symbols
can trigger the load of the extension, in case it decides to load on
demand. The extension name is implicitly an entry point, so we just
set the extra entry points.

This should cause no changes if the Crosswalk doesn't support the
interface for setting entry points yet -- like Crosswalk 1.
Add entry point information for extensions using old adapter

Entry point information is used by Crosswalk to know what symbols
can trigger the load of the extension, in case it decides to load on
demand. The extension name is implicitly an entry point, so we just
set the extra entry points.

This should cause no changes if the Crosswalk doesn't support the
interface for setting entry points yet -- like Crosswalk 1.
[SystemInfo] Fix coding style
[Bookmark] Remove old debug output
[SystemInfo][Display] Correct DPI property wrong type

The Tizen SystemInfo spec require dotsPerInchWidth and dotsPerInchHeigth as unsigned long, while
it were double that returned. This cause tct-systeminfo-tizen-tests case 173 and case 184 fail.

The fix is simply to convert the value to unsigned long before sending.
Bump version to 0.10
[SystemInfo] Use new C++ wrapper in common/extension.h

common::Extension and common::Instance are designed to replace ExtensionAdapater.
This commit change SystemInfo implementation to use the new wapper
[Common] Fix mistype on IO_ERR name
[Bluetooth] Add a way to validate more parameters

In many cases, an parameter with type 'object' is passed, and this
object is expected to have some parameters. We should be able to
verify that this object has the correct type of attributes.

Also add a simple Bluetooth address validator, using a simple regular
expression.