We need to include a notion of cluster instance in the cluster view id
to avoid at least the following scenario:

Client serializes a handle to a cluster which is at cluster view 22
Handle contains key DefaultPartition/HAJNDI/22

The cluster is totally restarted meaning the view reverts back to one.

The client now has a view id
DefaultPartition/HAJNDI/1

The client deserializes the handle, which will overwrite the correct cluster
view with the old invalid view.

This will also avoid the problem where a client talks to different clusters
with the same partition name.

Proposed solution:

1) At cluster formation (first node in cluster), create a cluster instance GUID
2) At cluster join (second+ node in cluster) get the GUID from the coordinator
3) Include this GUID in cluster view keys, i.e.
GUID/DefaultPartition/HAJNDI/1