The clientwrapper class masks granular object registration within
qml, and encourages code duplication between viewmodels(adapters)
and code lasagnafication and the misuse of declarative Qml.
Change-Id: I85fef214363e62e54fc0681282323ea4861000d6
Gitlab: #66
It seems concurrent calls to invokeMethod using qml component
object pointers can lead to access violations. These method
invocations can be replaced with a signal/slot mechanism.
This patch replaces only the invocations in conversationsadapter
and accountsadapter that are known to be problematic for now.
Some code cleanup is done for QmlAdapterBase derived classes.
Gitlab: #61
Change-Id: I72f47c9229a9bf42299ae52822c3a1a8c04eb423
