[Darwin] MTRDevice attribute cache handling of DataVersion does not handle subscription interruption well

[bzbarsky-apple]

Reproduction steps

Two issues:

1. We "commit" the new DataVersion to the in-memory store immediately, not at end of report, so if that store is used for a resubscribe (e.g. after a suspend/resume), we may have the "new" DataVersion but still "old" data for some attributes.
2. We are setting up the "cluster data to persist" as we go; on subscription interrupt we should probably clear it out so it does not get persisted by accident in a partially-received state.

Platform

darwin

Platform Version(s)

No response

Type

Manually tested with SDK

(Optional) If manually tested please explain why this is only manually tested

No response

Anything else?

No response