Added ability to measure clock offset from cluster

RPC servers and clients now both update a shared map of measured remote offsets.
Servers get this measurement from their attached clients. Servers
are given this ability because they don't always have their own client to the
remote node if that remote node has a client to them.

The server now passes a Context object to the rpc frameworks rather
than passing all 3 required fields individually.

Though the algorithm for measuring cluster offset is now implemented, the server does not yet actively measure cluster offset nor does it do anything with any offset measuring.
Thank you for trying to figure it out, anyway! I predict that the number of points in this will not be so large that time should be a concern. The one change I think I could make is in the second loop I could do this:

```
if endcount >= numClocks-falsechimers || upperbound <= lowerbound {
       break
}
```

Because it's already a given that the lowerbound < upperbound check will fail. So this bounds the complexity to N rather than 2N.