Support for chi/v5 Middleware Compatibility and Security Enhancements

[corinnesollows]

Hey KrakenD team 👋,

KrakenD v2.x currently depends on chi v4 for routing and middleware. Since v4:

1. Several middleware components (e.g. Logger, Recoverer) have known security vulnerabilities that are addressed in chi v5.
2. The broader Go ecosystem—including our services—has largely migrated to chi v5, making dependency alignment and shared middleware usage difficult.
3. Datadog and other tracing integrations no longer support chi v4, adding friction for observability.

🙏 Request:
Would the team consider:

• Upgrading KrakenD to chi v5 in an upcoming release?
• Or providing a compatibility layer to allow opt-in use of chi v5 middleware?

Thanks for all the great work on KrakenD!