cpp: use init method in message router for multiple constructors

Change-Id: Idbc335c814bb301b5a472e08b4a8ab2d91b69cba
cpp: use discovery types defined in model

* use discovery scope from model
* use discovery QoS from model, but only on cluster-controller side

Change-Id: Ifaca9dbf66f726beb04da65af5f9f4c7ec2a8f9b
cpp: local capabilities directory is also discovery provider

* local capabilities directory implements DiscoveryProvider interface
* registering local capabilities directory as DiscoveryProvider in CC
  rutime
* wrote test for DiscoveryProvider
* lookup with participant ID doesn't need discovery QoS
* added system services settings for discovery provider participant ID and
  authentication token
* added google-test PrintTo method for JoynrMessage in JoynrMessage source
  file
* removed legacy method getCapabilitiesForChannelId
* some formatting

Change-Id: I7cc2c679fa2c377b3b28128102d3c916ba7818e1
cpp: formatting

Change-Id: I305fe984a7e4402c12ce397ede3e7f1dca94dfd5
cpp: updating joynr version in cmake files to 0.7.0

Change-Id: I77f746f579d136a7bd900ecfcb9ab54fde689adc
cpp: Joynr messaging stub uses message sender

Until now, the joynr message sender used the communication manager to send
messages. The communication manager itself delegated the call to a message
sender.

With this patch the joynr messaging stub directly uses the message sender
to send messages.

For mocking purposes a IMessageSender interface is introduced.

The initialization of the message sender is still done by the communication
manager. The message sender is then exported using the getMessageSender
function. This will be changed in the following patches. The redundant send
functionality within the communication manager will also be removed.

Change-Id: I0a664978fae4d136bfc1e7aab8c774f337cbc800
cpp: Remove message sender from communcation manager

The functionality to send messages is removed from the communication
manager.

Change-Id: I470e2a9982f14e238ad025ce7dde56ae0c575a56
cpp: Rename message sender to http sender

Change-Id: Ia570fbfcb8fa16a7e2e6b9aaf81bf4299838b6c5
cpp: Long polling message receiver directly uses message router

Until now the long polling message receiver uses a message receiver
(IMessageReceiver) to forward received messages to the message router.

Now the messages are directly deserialized and forwarded to the message
router.

Change-Id: I6c15cf7e648199fa9694c2f6d13a4f8288356a18
cpp: Remove message dispatcher from communication manager

The message dispatcher is not needed anymore as the messages are forwarded
directly to the message router.

Change-Id: I2611c9f7318b54c2e4d74991f320737d89f01702
cpp: Delete obsolete LongPollMessageSerializer

The LongPollMessageSerializer is not used anymore, so the classes are
removed from the project.

Change-Id: I66f67cde3659eccca7d439c19a913ab9f028de13
cpp: Rename http communication manager to http receiver

Change-Id: Ie8010879fb04d474d050495dce3b2eb1b6119104
cpp: Rename ICommunicationManager to IMessageReceiver

Change-Id: Ic96fc3b5fef8af24b44c1b27576ec0ba16719c61
cpp: Protect routing table with mutex

Change-Id: Ic7b442c084d1457e3cedda650d99fe8f82afe943
java: tests to track duplicate messages bug in bounce proxy

* on concurrent requests, message is sent in long poll response twice
* assert statement to separate bug from other test failures
* additional test that only sends and receives messages concurrently

Change-Id: I6ac246864d3cb328ab897c0b14d08682366d0569