Closes #6768

Why is this the best possible solution? Were any other approaches considered?

This is a result of the discussion we had in the issue. To sum up:
When Collect is set to only access own Entities, deleted Entities on Central may stay on the device if the hash doesn’t change. The team debated whether Central should update hashes on every delete or whether Collect should always run an integrity check. The decision: treat the hash as list contents and have Collect run an integrity check whenever offline Entities exist.

How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?

With this change, during form sync, even if the entity list hash hasn’t changed, Collect will use the integrity URL whenever offline entities exist to check for deletions and clear them if needed. The only known case is described in the issue. If you can think of other ways to reproduce it, please share them.

Do we need any specific form for testing your changes? If so, please attach one.

The form from the issue.

Does this change require updates to documentation? If so, please file an issue here and include the link below.

No.

Before submitting this PR, please make sure you have:

• added or modified tests for any new or changed behavior
• run ./gradlew connectedAndroidTest (or ./gradlew testLab) and confirmed all checks still pass
• added a comment above any new strings describing it for translators
• added any new strings with date formatting to DateFormatsTest
• verified that any code or assets from external sources are properly credited in comments and/or in the about file.
• verified that any new UI elements use theme colors. UI Components Style guidelines