Add support for administrative levels search parameters on LocationHierarchy endpoint

[lincmba]

Resolves #64

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-commenter]

Codecov Report

Attention: Patch coverage is 49.39759% with 42 lines in your changes missing coverage. Please review.

Project coverage is 44.89%. Comparing base (d7eeb69) to head (7d9ba8b).
Report is 14 commits behind head on main.

Files	Patch %	Lines
...teway/plugins/LocationHierarchyEndpointHelper.java	53.24%	29 Missing and 7 partials ⚠️
...ay/plugins/endpoint/LocationHierarchyEndpoint.java	0.00%	5 Missing ⚠️
...way/plugins/PractitionerDetailsEndpointHelper.java	0.00%	1 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##               main      #66      +/-   ##
============================================
+ Coverage     43.81%   44.89%   +1.08%     
- Complexity      106      123      +17     
============================================
  Files            15       15              
  Lines          1075     1156      +81     
  Branches        120      143      +23     
============================================
+ Hits            471      519      +48     
- Misses          545      570      +25     
- Partials         59       67       +8     

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

[lincmba]

What is a reasonable default maximum admin level depth?

[dubdabasoduba]

I am not sure we can have a max level because countries have different hierarchies. I know we can have the min which is 0 but I don't think we can restrict the max

In case the max is not defined we are supposed to fetch the whole hierarchy to the end of the node

[lincmba]

Seeing this is how the type element is represented:

"type": {
    "coding": [
      {
        "system": "http://example.org/fhir/CodeSystem/location-type",
        "code": "1",
        "display": "Level 1"
      }
    ],

querying directly with conditions like code is greater than 5 on a string representation of a code is not possible. FHIR does not support such numeric comparisons on string fields directly within the query. So, to handle this, I have implement post-query filtering in the application logic.

This commit addresses that 7d9ba8b
This means, api requests with adminstrativeLevelMax set will be more optimized than those without.

[dubdabasoduba]

This makes sense. Can we review the performance with what we have as we think of how to address this?