Fix wrong behavior about return value of shortcut request

Fix wrong behavior about return value of shortcut request

 - Currently, It is a structure in which the caller can not get
   a proper return value when there is a request such as
   shortcut add or remove.
 - The caller generates a request-id for each shortcut, passes the id
   to data-provider-master and passes the return vallue to caller
   using the id in the data-provider-master daemon.
 - related patch : https://review.tizen.org/gerrit/#/c/114091/

Signed-off-by: seungha.son <seungha.son@samsung.com>
Change-Id: I30791a7a1309df8d9473a373e785bdc9ceb1f62a