changing doHeartbeat to always call addProposedMember(h20) with incoming node. Currently it's conditioned on "not in cloud". Commented out the old position, in case we need to return to that.

    // Failing case would be if our cloud had a better(lesser) leader than our current LEADER
    // If we never updated LEADER to that better value, we can have steady state with different nodes having
    // different LEADER values.
    // Since we ignore proposals not from LEADER, that's a steady state fail.
    // So always try to add all incoming heartbeats to PROPOSED_MEMBERS to guarantee that we
    // always have LEADER matching what others see. (or we could compare LEADER to cloud[0] when we
    // add a cloud..that would be better performance wise. Or just an assertion, but
    // this was simpler/more of a guarantee.

    addProposedMember(h2o);

passes my 2 machine home testing. as good as anything yesterday. No fails. Maybe this will help Michal's failure from today. Although I still think the problem of cloud id/cloud member Accepted packets may need to be addressed (discussed with cliff)

Note the change doesn't change the theoretical underpinnings of how the overall algo should be working.