[Location Hierarchy] Add Support for Recreating Ancestor Lineage Across All Locations

[dubdabasoduba]

Context

• Enhance the LocationHierarchy endpoint to support two new query parameters:
  • recreate-lineage=true – Triggers the recalculation and updating of ancestor lineage tags for all Location resources in the hierarchy.
  • hierarchy-root-location=uuid – Specifies the UUID of the root location for the hierarchy to be updated.
• If the hierarchy-root-location parameter is provided, the lineage recalculation process will start from the specified root location instead of automatically identifying the root.

Implementation

• When the LocationHierarchy endpoint is called with recreate-lineage=true, the system should initiate a lineage recalculation process. The process should traverse the location hierarchy starting from the root location.
• The root location must be explicitly specified using the hierarchy-root-location parameter.
  • his parameter is mandatory. If it is not provided, the endpoint should return an error response.
• The lineage identification and addition should work as described here [Location Hierarchy] Enable storing ancestor tags on all locations. fhir-gateway-extension#110

Acceptance Criteria

• The location hierarchy endpoint should have the ability to recreate the location ancestor tags.
• The hierarchy-root-location is a mandatory parameter on the API if recreate-lineage=true is available.

[pld]

This should not be the gateway's responsibility. This seems reasonable in a tooling script

[dubdabasoduba]

This should not be the gateway's responsibility. This seems reasonable in a tooling script

I will be moving this to the tooling repo.

[pld]

As we discussed we need to share this between both tooling and the gateway so the majority of this code goes into a shared library