Heartbeat code still uses timestamp rather than logical clock to decide if config is up-to-date

There are, alas, many places where Flume is still using physical timestamps rather than logical ones for config versions.

e.g. in MasterClientServer.java, in heartbeat(...)

if (cfg == null || version < cfg.getTimestamp())

{ configChanged = true; // version sent by node is older than current, return true to force config // upgrade }