Set MedicationRequest status to COMPLETE instead of STOPPED

[lmd59]

This PR fixes a discrepancy in how MedicationRequests are created by the synthea R4 export. The previous code was setting the MedicationRequest to STOPPED if the medication has a valid stop value. But looking at the MedicationRequest status valueset, stopped means:

Actions implied by the prescription are to be permanently halted, before all of the administrations occurred. This should not be used if the original order was entered in error

Essentially this seems to mean that the request was stopped rather than that the medication itself was stopped. For most synthea modules, the intent is for medication.stop to get set to something other than 0L when the medication is completed. As such, we want to set the MedicationRequest to COMPLETED for this case to capture the intent of those modules.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 77%. Comparing base (e83ae2f) to head (ebde152).
Report is 13 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff            @@
##             master   #1572   +/-   ##
========================================
  Coverage        77%     77%           
- Complexity     4005    4023   +18     
========================================
  Files           178     178           
  Lines         25169   25199   +30     
  Branches       3591    3594    +3     
========================================
+ Hits          19485   19543   +58     
+ Misses         4557    4541   -16     
+ Partials       1127    1115   -12     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

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