FHIR Gateway Enhancements

[ndegwamartin]

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

In this PR

• Fix REL sync strategy Caching bug
• Refactor to support returning all paginated results
• Refactor REL upstream fetch to single request
• Pagination count bumped to 200
• Release version 2.1.2

Engineer Checklist

• I have written Unit tests for any new feature(s) and edge cases for
  bug fixes
• I have added documentation for any new feature(s) and configuration
  option(s) on the README.md
• I have run mvn spotless:check to check my code follows the project's
  style guide
• I have run mvn clean test jacoco:report to confirm the coverage report
  was generated at plugins/target/site/jacoco/index.html
• I ran mvn clean package right before creating this pull request.

[codecov]

Codecov Report

Attention: Patch coverage is 78.50467% with 46 lines in your changes missing coverage. Please review.

Project coverage is 67.61%. Comparing base (01da39e) to head (23ce64a).

Files with missing lines	Patch %	Lines
.../fhir/gateway/plugins/PermissionAccessChecker.java	27.58%	20 Missing and 1 partial ⚠️
...ister/fhir/gateway/plugins/SyncAccessDecision.java	84.42%	10 Missing and 9 partials ⚠️
.../org/smartregister/fhir/gateway/plugins/Utils.java	89.28%	3 Missing and 3 partials ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##               main      #92      +/-   ##
============================================
+ Coverage     61.54%   67.61%   +6.07%     
- Complexity      206      247      +41     
============================================
  Files            16       16              
  Lines          1412     1541     +129     
  Branches        164      184      +20     
============================================
+ Hits            869     1042     +173     
+ Misses          458      402      -56     
- Partials         85       97      +12     

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

---

🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests

[dubdabasoduba]

I think this is a great idea but should only affect the requests made after the configs are done loading. I am not sure how we can separate that.

We are currently getting this error for good requests that should work without _syncLocation because they are being requested via that composition.

[ndegwamartin]

@dubdabasoduba how should the Gateway respond for requests that are using REL but do not have _syncLocation specified?

[dubdabasoduba]

It should return an error saying that the sync locations are not set. However, We should ensure the requests made from the composition resources don't throw that error. Those requests are not affected by the sync strategies.

[ndegwamartin]

I think those coming from composition should be ignored on the Allowed Queries or the Ignore Sync filter configuration file.