Suspend functions to evaluate fhirpath expressions

[LZRS]

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

Fixes #2677

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]

Actually what I notice is that these "non-suspend" functions are being invoked from suspend functions only.

So instead of making each function suspend what if we make the source of flow to run on default dispatcher ? In class QuestionnaireViewModel, we could add flowOn operator to the questionnaireStateFlow

[LZRS]

Actually what I notice is that these "non-suspend" functions are being invoked from suspend functions only.

So instead of making each function suspend what if we make the source of flow to run on default dispatcher ? In class QuestionnaireViewModel, we could add flowOn operator to the questionnaireStateFlow

Okay, cool. I can try it out, not sure how we will handle passing testDispatcher for tests though. That is, in the QuestionnaireViewModelTest