chore: adds conditional persistence propagation

[tanderson-ld]

Requirements

• I have added test coverage for new or changed functionality
• I have followed the repository's pull request submission guidelines
• I have validated my changes against all supported platform versions

Related issues

SDK-1622

Describe the solution you've provided

Adds shouldPersist to change set classes.

---

Note

Medium Risk
Touches core data ingestion and persistence paths (polling/streaming, write-through, recovery) and changes DataStoreTypes value semantics; risk is mainly incorrect persistence gating or missed persistence in edge cases, but changes are straightforward and well-tested.

Overview
Adds a shouldPersist flag to DataStoreTypes.FullDataSet and DataStoreTypes.ChangeSet and threads it through sorting, translation, and store update flows.

Polling/streaming/FDv2 changesets are now explicitly marked shouldPersist=true, while file-based data is marked false; WriteThroughStore and PersistentDataStoreWrapper use this to skip writes to persistent stores (including during recovery) when data is non-authoritative. InMemoryDataStore tracks and re-exports the latest shouldPersist value so downstream persistence decisions are consistent, and tests are updated/expanded accordingly.

^{Written by Cursor Bugbot for commit 35a1038. This will update automatically on new commits. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}