UHFQA retrieve acquisitions can produce wrong results

Spawned by !203 (merged) .

This is one of the trickier implementations for the ZI backend. As we use the LabOne server to communicate and retrieve acquisitions, there are cases when the acquisition call has timed out. When that happens, LabOne just spits out the last successful acquisition without any warning to the user.

!203 (merged) will implement a workaround to this issue.

Hence, we need to restart the entire instrument coordinator to retrieve the acquisition again whilst checking if we got a duplicated result.

The real solution would be to properly check if the acquisitions are done before retrieving data from the right node. The discussion on !203 (merged) contains references to the implementation in PycQED that ensures the nodes are properly checking the acquisition is completed before getting the values of the acquisition nodes.

Looking into scheduler itself, it appears the the acquisition resolvers only get the value of the node without doing the right waiting for completion. This requires a bit more digging into to resolve properly.