Don't update entity if it doesn't exist in the list

[seadowg]

Closes #6031
Closes #6109
Blocked by getodk/javarosa#763

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

Not a lot to discuss here! We'd previously exposed the entity "action" from JavaRosa, but weren't using it yet. The big change here is that we detect if the entity doesn't exist if the action is "update" and skip saving.

Additionally, we ignore saving entities that don't have an ID to fix #6109.

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?

This a fairly small set of change, so just testing the issues are fixed is probably enough here.

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

[WKobus]

Tested with success!

Verified on a device with Android 14

Verified cases:

• Acceptance criteria from Prevent updates to entities that don't appear in entity list #6031 are met
• Issue Crash of the app after sending a draft version of trees update form #6109 does not occur
• Updating entities through update form
• Updating entities by manually providing ID and Version

[srujner]

Tested with success! with @dbemke

Verified on a device with Android 10,13