fix: correct stripPath and addPrefix middleware order

[Siumauricio]

Summary

• Swaps the order of stripPrefix and addPrefix middleware in Traefik router config so stripPrefix runs first
• When both stripPath and internalPath are set, requests like /public/api/users now correctly resolve to /app/v2/api/users instead of /app/v2/public/api/users
• Adds test verifying middleware ordering when both options are active

Closes #4061

Greptile Summary

This PR fixes a middleware ordering bug in Traefik router configuration where addPrefix was registered before stripPrefix, causing requests like /public/api/users to incorrectly resolve to /app/v2/public/api/users instead of /app/v2/api/users. The fix swaps the push order so stripPrefix is always registered first, and adds a focused test to lock in the correct ordering.

Confidence Score: 5/5

This PR is safe to merge — it corrects a clear middleware ordering bug with no regressions introduced.

The change is minimal and targeted: a two-block swap in a single function, backed by a new test that directly asserts the correct ordering. The logic is straightforwardly correct for Traefik's sequential middleware model, and no existing tests are broken. No P0/P1 findings identified.

No files require special attention.

_{Reviews (1): Last reviewed commit: "fix: swap stripPrefix and addPrefix midd..." | Re-trigger Greptile}