use a common poller thread for modules sharing io

When several poller threads are using the same io, the resposivity
of client requests is reduced, as every thread first finishes
its pending communication requests, before it is the turn of the
request thread. This is solved by using one common poller thread
for all modules sharing the same communicator.

+ fix an issue with overriding a property with a parameter, as
  this is the case for pollperiod (cfg was applied to property
  instead of overriding parameter)
+ separate setFastPoll arguments into flag and fast interval
+ fix missing announceUpdate call when read function fails
+ fix mechanism for triggering polls after an io connection
  reconnected again.

Change-Id: I1115a61fae3de80d18416e61f40b52a0eebb637c
Reviewed-on: https://forge.frm2.tum.de/review/c/sine2020/secop/playground/+/28021
Tested-by: Jenkins Automated Tests <pedersen+jenkins@frm2.tum.de>
Reviewed-by: Markus Zolliker <markus.zolliker@psi.ch>

secop/io.py

@@ -118,6 +118,7 @@ class IOBase(Communicator):
 
     def earlyInit(self):
         super().earlyInit()
+        self._reconnectCallbacks = {}
         self._lock = threading.RLock()
 
     def connectStart(self):
@@ -171,10 +172,7 @@ class IOBase(Communicator):
 
         if the callback fails or returns False, it is cleared
         """
-        if self._reconnectCallbacks is None:
-            self._reconnectCallbacks = {name: func}
-        else:
-            self._reconnectCallbacks[name] = func
+        self._reconnectCallbacks[name] = func
 
     def callCallbacks(self):
         for key, cb in list(self._reconnectCallbacks.items()):