MS-1225 Do not reset local data when sync frequency changes

[luhmirin-s]

JIRA ticket
Will be released in: 2025.3.0

Root cause analysis (for bugfixes only)

First known affected version: 2025.3.0

• Data reset was triggered on any change within down.simprints configuration

Notable changes

• Remove the full object comparison from the check; we only care about partitioning.
• Add unit test to ensure frequency checks do not trigger the wipe.

Testing guidance

• Set the project to sync periodically.
• Create some local data.
• Change to another sync frequency and sync configuration.
• Check that all are present on device and were not re-downloaded

Additional work checklist

• Effect on other features and security has been considered
• Design document marked as "In development" (if applicable)
• External (Gitbook) and internal (Confluence) Documentation is up to date (or ticket created)
• Test cases in Testiny are up to date (or ticket created)
• Other teams notified about the changes (if applicable)

[BurningAXE]

Maybe we can add tests (or update this one) to check that other fields inside simprints don't cause a reset, just in case.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
80.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud