Implement multitenancy support

[alexdunnjpl]

🗒️ Summary

Fixes outstanding issues with AOSS support

Wraps all instances of 'registry' and 'registry-refs' with a resolution function which returns an altered string iff env var MULTITENANCY_NODE_ID is set to a non-empty value

⚙️ Test Data and/or Report

Initially: Manually tested in the empty-value case. Tested in DEV MCP against registry-en-delta
Changes have been cherry-picked from #122, and not tested yet - must be tested manually in DEV MCP

♻️ Related Issues

fixes #120
related to #60

[alexdunnjpl]

@jordanpadams @tloubrieu-jpl what's the priority on getting this tested and merged?

[jordanpadams]

@alexdunnjpl let's talk about this at the breakout, but I added this ticket associated with this to the Registry API MVP. I really don't think we can deploy the API without have sweepers up an running (or at least the API will not work for several endpoints)

[alexdunnjpl]

@jordanpadams I'll put testing this top-of-list, then

[alexdunnjpl]

Testing blocked until EC2-attachable role created in MCP-PROD for use in tests.

@sjoshi-jpl has opened a ticket (could you link it here when you get a minute?) as only SAs have access.

sweepers policy will be temporarily attached to the new role to allow manual testing in EC2, then unattached once it's confirmed that sweepers can function with that policy.

[alexdunnjpl]

Tested on MCP prod. Currently running against MCP indices to allow for immediate API deployment without blockage by ECS sweepers deployment. Blocked by VPN issues