Compose benchmark app crud

[LZRS]

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

Fixes #2812

Based on #2817

Description
Clear and concise code change description.

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

Type
Choose one: (Bug fix | Feature | Documentation | Testing | Code health | Builds | Releases | Other)

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).

[MJ1998]

Do we need runBlocking because of the usage of measureTime and measureTimedValue.
Because the flow of execution is anyway sequential and if these functions were suspend then we wouldn't need the runBlocking.
I would recommend to manually capture the duration in a suspended helper function instead of using measureTime, measureTimedValue. - This way you can avoid using runBlocking.

[LZRS]

Do we need runBlocking because of the usage of measureTime and measureTimedValue. Because the flow of execution is anyway sequential and if these functions were suspend then we wouldn't need the runBlocking. I would recommend to manually capture the duration in a suspended helper function instead of using measureTime, measureTimedValue. - This way you can avoid using runBlocking.

Cool, yeah that makes sense.

[LZRS]

@MJ1998 I've updated the PR to include the changes you suggested