982: Handle 'nested locations/endpoints' in Service Discovery setup - research & POC

Handle 'nested locations/endpoints' in service routing

Currently, we have an ability to redirect to our services under the same host using location prefixes, like localhost/requisition or localhost/example

After API discussions: we foresee endpoints like /facility/(id) map to the reference data service and /facility/(id)/requisitions map to the requisition service. There is a need to handle such scenarios in the Nginx + Consul setup.

We've briefly decided to hold this off until referencedata service is extracted from requisition.

Acceptance criteria

• (general example) our configured server redirects /facility/(id)/requisitions request to requisition service and not falsely to reference data service