Fix EZP-23337: New stack does not generate 301 redirects for wrongly cased URLs

This PR revolves issue https://jira.ez.no/browse/EZP-23337

Case correction redirection was not implemented.

This implements it, with one improvement over Legacy Stack behaviour. In LS, for custom resource alias (e.g. custom alias on `/content/search` resource), case-incorrect URL would result in the redirection to the resource itself, rather than to the case-corrected custom alias. That seems incorrect, and behaviour here is therefore redirection to the case-corrected custom alias.

Note: forward (redirect) flag has precedence, so requesting case-incorrect URL for the forwarding custom alias will not result in redirection to the case-correct alias but to the original resource directly.

Tests: unit tests + manual integration testing.
FWIW it was already implemented like that and that is also how Legacy Stack handles it.
IMHO it would be weird to have `/hello` redirecting to `/` and `/hello/search` working normally (from the example in my previous comment).