Resource creation using AllChangesSquashedBundlePost upload strategy.

[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

• [x] I have read and acknowledged the Code of conduct.
• [x] I have read the Contributing page.
• [x] I have signed the Google Individual CLA, or I am covered by my company's Corporate CLA.
• [x] I have discussed my proposed solution with code owners in the linked issue(s) and we have agreed upon the general approach.
• [x] I have run ./gradlew spotlessApply and ./gradlew spotlessCheck to check my code follows the style guide of this project.
• [x] I have run ./gradlew check and ./gradlew connectedCheck to test my changes locally.
• [x] 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).