[NetworkBearer] Handle API methods separately

The previous implementation was trying to share as much as possible code
between the Request and Release methods due to its similarities. It only
made the code more complex and the validation of the input parameters more
difficult.
Bump version to 0.4
[SystemSetting] Fix SystemSetting API failures on tct test siute

Fix the validation of input parameters and throw the right
error when the invalid values are passed to getProperty()
or setProperty() methods.

Fixes #320.
Merge pull request #206 from nagineni/input_validation

[SystemSetting] Fix SystemSetting API failures on tct test siute
Bump version to 0.5
[SystemInfo] Get values for getCapabilities() using updated Tizen capi
[SystemInfo][Cpu] Fixes #125 for compile warnings
[SystemInfo] Add function ParseBoolean() for getCapabilities()
Merge pull request #203 from fyraimar/master

[SystemInfo] Get values for getCapabilities() using updated Tizen capi
[Time] Add getTimezoneOffset, getTimeWithOffset and fix get/set UTCs

getTimezoneOffset replaced getTimezoneRawOffset, this new one calculates
the DST offset.

Fix getters and setters of UTCs using getTimeWithOffset.
[Time] Change getDSTTransition return from undefined to null

Based on the tests:

TZDate_getNextDSTTransition.html
TZDate_getPreviousDSTTransition.html
[Time] Properly handle getTimeFormat
Merge pull request #192 from ricardotk/wip

[Time] Add and fix features
Merge pull request #205 from tmpsantos/refactoring

[NetworkBearer] Handle API methods separately
Merge pull request #204 from fyraimar/fix_cpu_compilewarning

[SystemInfo][Cpu] Fixes #125 for compile warnings
[SystemInfo] Fixes #128 and also resolves #130, the type mismatch bugs
Merge pull request #208 from Ryan--Yang/bug-fix

[SystemInfo] Fixes #128 and also resolves #130, the type mismatch bugs
[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.