Resource consolidation after using the AllChangesSquashedBundlePost upload strategy for resource creation.

[santosh-pingle]

IMPORTANT: All PRs must be linked to an issue (except for extremely trivial and straightforward changes).

Fixes #2499

Description
The resource is created locally, and the AllChangesSquashedBundlePost is used to synchronize the resource with the FHIR server. In return, the server sends a response containing the resource metadata and the newly assigned resource ID as BundleEntryComponent in the Bundle. Subsequently, the local database is updated with the provided resource.

Upload strategy : AllChangesSquashedBundlePost
Discard the local changes from LocalChangeEntity table.
Update the resource with the received resourceId and meta data in the local database.
Update the resource with the received reference id in the local database.

Note: This change does not handle resource consolidation if multiple bundles are sent in the upload request to create resources at the server.

Alternative(s) considered
Have you considered any alternatives? And if so, why have you chosen the approach in this PR?

Type
Choose one: Feature

Screenshots (if applicable)

Checklist

• I have read and acknowledged the Code of conduct.
• I have read the Contributing page.
• I have signed the Google Individual CLA, or I am covered by my company's Corporate CLA.
• I have discussed my proposed solution with code owners in the linked issue(s) and we have agreed upon the general approach.
• I have run ./gradlew spotlessApply and ./gradlew spotlessCheck to check my code follows the style guide of this project.
• I have run ./gradlew check and ./gradlew connectedCheck to test my changes locally.
• I have built and run the demo app(s) to verify my change fixes the issue and/or does not break the demo app(s).

[nsabale7]

Please look into the meta tag overwriting issue, as we have encountered this problem.

[jingtang10]

Thanks @santosh-pingle - just left some more comments.

Perhaps the most critical comment is that the new db function needs to be tested.

@FikriMilano also fyi. Thanks!

[joiskash]

I am not sure if this is already discussed, but here is use case that will need to be supported. We should discuss if there are any race conditions and potential OOMs -
CHW is offline for 2 weeks
Visits 30 houses per day
Each house has 4 family members
Each registration results in 30 resources per family member
This will create a total of 2x7x30x4x30 = 50,400 resources with references. Let us assume that there are no resources with base64 binary data. Each resource will roughly be 5KB that's roughly 100 MB of data to upload. 3G upload speed is around 0.4 MB/s. So this should take roughly 5 minutes to upload + post sync processing time. We could have some documentation around the performance of using POST vs PUT and the repercussions based on this.

[santosh-pingle]

I am looking into the review comments.