SyncParametersClient can't be used in component node

Because SyncParametersClient calls spin_until_future_complete it can't be used in component nodes.

A workaround for this might be to have some way of discovering if the node is a component and then just calling get() on the future instead of trying to spin the node (as the Node should already be added to an executor and executing). Another option would be to leave spinning the Node on an executor up to the implementer of the Node (expect they are spinning it already when they call methods like set_parameters) and change the implementation of SyncParametersClient to block forever (by waiting on the future) if the user failed to start the executor on a separate thread first.

This workaround might not work during initialization if the component manager doesn't start the executor on a separate thread before loading the component nodes.