Restoring event subscriptions code is faulty

[yallie]

Zyan currently uses subscription counters and checks if they match on client and server. But we can't rely on them if we're making concurrent calls with subscriptions/unsubscriptions. Zyan detects the mismatch and starts re-subscribing even if it actually doesn't need to. It doesn't break anything, just generates some parasite network traffic.

[yallie]

Counter is not enough for detection subscription mismatch.
A server and a client might have different set of active subscriptions of the same length.
Let's compare fingerprints/sha hashes of the active delegate correlation sets.

[yallie]

TODO:

• Use checksums instead of the simple subscription counter
• DynamicEventWire.CancelSubscription doesn't lock the wiring list
• ZyanConnection.ReconnectRemoteEvents swallows exceptions
• ZyanProxy.ReconnectRemoteEvents still calls ZyanConnection.CheckRemoteSubscriptionCounter
• Batch resubscriptions — IZyanDispatcher.ReconnectEventHandlers method
• Add a way to trace re-subscriptions — ZyanComponentHost.SubscriptionsRestored event