Fix Quest CI test failure

[Rkareko]

IMPORTANT: Where possible all PRs must be linked to a Github issue

#3725

Engineer Checklist

• I have written Unit tests for any new feature(s) and edge cases for bug fixes
• I have added any strings visible on UI components to the strings.xml file
• I have updated the CHANGELOG.md file for any notable changes to the codebase
• I have run ./gradlew spotlessApply and ./gradlew spotlessCheck to check my code follows the project's style guide
• I have built and run the FHIRCore app to verify my change fixes the issue and/or does not break the app
• I have checked that this PR does NOT introduce breaking changes that require an update to Content and/or Configs? If it does add a sample here or a link to exactly what changes need to be made to the content.

Code Reviewer Checklist

• I have verified Unit tests have been written for any new feature(s) and edge cases
• I have verified any strings visible on UI components are in the strings.xml file
• I have verifed the CHANGELOG.md file has any notable changes to the codebase
• I have verified the solution has been implemented in a configurable and generic way for reuseable components
• I have built and run the FHIRCore app to verify the change fixes the issue and/or does not break the app

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 29.7%. Comparing base (1542bb7) to head (43ea9f7).
Report is 5 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main   #3726     +/-   ##
=========================================
- Coverage     37.9%   29.7%   -8.2%     
+ Complexity    1157     899    -258     
=========================================
  Files          287     287             
  Lines        15504   15505      +1     
  Branches      2730    2733      +3     
=========================================
- Hits          5884    4619   -1265     
- Misses        8776   10321   +1545     
+ Partials       844     565    -279     

Flag	Coverage Δ
engine	60.7% <0.0%> (-0.1%)	⬇️
geowidget	16.0% <0.0%> (ø)
quest	11.3% <0.0%> (-13.4%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

see 34 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[FikriMilano]

Would it worth to try adding a 'delay()' or any fix to the flaky test, assuming it's using a coroutine, and see if that'll make the test more robust?

Say, the test/CI passes 3x?