To support Cynara-based permissions checking

(1) Add class TizenCynaraChecker to deal with Cynara lib.
(2) Embbed TizenCynaraChecker into the "Application::GetPermission" to integrate with existent logic as well as possible.
(3) Add mapping between permissions name and Tizen privileges.
(4) Take Geolocation as a sample to use it.

This patch is a refactor of https://github.com/crosswalk-project/crosswalk/pull/2525 to integrate with existent code of Crosswalk, as we've resolved all the problems of invoking Cynara interfaces in that pull request.
@PeterWangIntel
Function `cynara_check()` should always return either `CYNARA_API_ACCESS_ALLOWED` or `CYNARA_API_ACCESS_DENIED`. These are also the only two policy types supported natively by cynara. But additional policy types can be handled by cynara plugins. Those plugins will be 3rd party code loaded by cynara. This code will be responsible for resolving queries into ALLOW/DENY response that will be used by cynara as response. One of such plugins that is planned for Tizen is plugin for asking user through the system pop-up.
Function `cynara_check()` will return to the caller with result after it gets that result from appropriate plugin, if the policy requires that. You should assume that it may take a long time, if the plugin waits for a user input.