Fill fhir auth

[KeeyanGhoreshi]

Describe your changes

Use with cds-hooks branch fhirAuth to get the fhirAuthorization populated in the hook. Make sure to set the environment variable to true as the default behavior is false, which will not add the fhirAuthorization.

FhirAuthorization information is pulled from the fhirclient.

Note that prettier will be complaining because cds-hooks submodule is not updated and it is based off dev branch still. It will go away once the cds-hooks branch is merged.

Issue ticket number and Jira link

REMS-364

Checklist before requesting a review

• I have performed a self-review of my code
• Ensure the target / base branch for any feature PR is set to dev not main (the only exception to this is releases from dev and hotfix branches)

Checklist for conducting a review

• Review the code changes and make sure they all make sense and are necessary.
• Pull the PR branch locally and test by running through workflow and making sure everything works as it is supposed to.

Workflow

Owner of the Pull Request will be responsible for merge after all requirements are met, including approval from at least one reviewer. Additional changes made after a review will dismiss any approvals and require re-review of the additional updates. Auto merging can be enabled below if additional changes are likely not to be needed. The bot will auto assign reviewers to your Pull Request for you.

[jtquach1]

As far as I can tell, the order-select hook appears to send properly via the MedicationRequest dropdown.

• With REACT_APP_SEND_FHIR_AUTH_ENABLED = false in my .env.local:
  I can see that for all 3 drugs, the fhirAuthorization field is not present.
• With REACT_APP_SEND_FHIR_AUTH_ENABLED = true in my .env.local:
  I can see that for all 3 drugs, the fhirAuthorization field is present.

Besides that, just requested minor changes.

[jtquach1]

Also made a PR to update the corresponding Markdown file in mcode/rems-setup with REACT_APP_SEND_FHIR_AUTH_ENABLED and other new env vars.

mcode/rems-setup#18