[FEATURE] Dedicated URL Path for EZID Resolution Requests

[adambuttrick]

Describe the problem you would like to solve The current EZID resolution logic processes all requests through the top-level URL, causing unnecessary logging of high-volume resolution requests. This extra logging creates excessive database operations, impacting overall system performance and stability.

Describe the solution you'd like Update the resolution logic to use a specific, lower-level URL path for resolution requests.

1. Create a new, dedicated URL path for resolution requests.
2. Modify the EZID application to route resolution requests to this new path.
3. Update Matomo configuration to exclude this new path from logging.
4. Ensure that non-resolution requests continue to be logged as before.
5. Implement appropriate redirects or communication to ensure existing integrations aren't broken by this change.

Who would benefit from this feature?

• End Users: Improved system performance reliability for all EZID services.
• Devops: Easier time managing system resources and troubleshooting performance issues.
• Devs: Benefit from a cleaner separation of concerns in the application.

[adambuttrick]

@datadavev Could you provide any additional context or clarifications here?

[adambuttrick]

Decoupling from epic as decision was made to move to OpenSearch, making this a service-level improvement.