Correct the behavior of other ROS classes for serial_bridge

[maxsvetlik]

The Subscriber class works as intended bidirectionally- the local machine is expected to have those topics already available, subscribes to them internally and then relays them over the socket to the bridge on the remote, which in turn makes Publisher objects to handle the incoming flow.

Ideally Publisher objects could handle the opposite case, i.e. the local machine specifically wants to listen to a particular topic on a remote bridge.

This functionality should be close to working in its current state, but doesn't quite work as intended.
Other classes have not been thoroughly tested at all ( ServiceClient, ServiceServer ) as their use for close proximity, multi agent interactions is lower priority than data sharing. Even so, these should be tested and modified if needed for completeness.