Resolving an entity modifies OpenRosa hash and ETag of entities CSV

[matthew-white]

The entities CSV has an OpenRosa hash and ETag based on the latest createdAt or updatedAt among the entities. When the OpenRosa hash changes, OpenRosa clients will re-download the entities CSV. Right now, if an entity is marked as resolved, its updatedAt timestamp is changed even if no new version of the entity is created. That has the effect of changing the OpenRosa hash and ETag. I think it is the correct behavior to change the updatedAt timestamp in this way, as that's similar to what we do with submission review states. However, I think we should try to find a way to avoid the side effect of re-download to OpenRosa clients.

This issue seems thematically related: getodk/central-backend#1041. That said, the two issues might end up being pretty separate.

[matthew-white]

We've decided not to address this issue as part of v2023.5. We might just close it at some point:

• It's not clear how common it will be for a user to mark an entity as resolved without updating it.
• Long-term, the goal is for OpenRosa clients to download changes to the entity list progressively rather than re-download the list each time. Once that's in place, it's not clear that this will still be much of an issue. Maybe clients will re-download the individual resolved entities, but they won't be re-downloading the entire entity list.