Added loghandler to handle log messages from the Client Library with …

[urmahp]

…ROS2 logging

This implementation wont be used until the client libraries macros are updated to not use console_bridge. However once the console bridge dependency has been removed from the client library, messages logged in the client library will be logged with ROS2 logging.

This will also fix issue #107

[destogl]

A few minor comments. The code looks clean and good. I am just not sure about its purpose. Does it mean that in the driver those internal macros should be used instead of those defined in the rclcpp library?

[urmahp]

A few minor comments. The code looks clean and good. I am just not sure about its purpose. Does it mean that in the driver those internal macros should be used instead of those defined in the rclcpp library?

The driver should just continue to use macro's defined inside the rclcpp library.

This is just a handler to handle messages logged inside the client library with ROS2 logging functionality. This means that messages from the client library will be handled the same way as messages logged inside this driver. See logging configuration in the client library.

If console_bridge is found on the system when building the client library, logging commands will be done by console bridge. This is currently the case when building the client library together with the ROS2 driver. Therefore these changes wont have any affect until the console_bridge dependency is removed from the client library. I have created a PR for removing this dependency from the client library. Once this dependency has been removed from the client library these changes will log all messages from the client library with ROS2 logging.

[destogl]

@urmahp I am OK to merge this. Only I don't see where #107 is solved. Can you point me to those lines?