Edge runtime routes throw 500 error on trailing slash mismatch

[ascorbic]

If trailing slash in disabled, requesting an edge runtime route with a trailing slash will throw a 500 error. This is because the matcher pattern strictly matches just the route without the slash, meaning the site tries to serve the route from the origin which will fail. The expected behaviour is to redirect to the canonical version.

The fix is the trailing slash fix as indicated in #1448, however this may need to happen before the edge router is implemented.

e2e test: streaming-ssr

[ascorbic]

I think that once excluded_route support for edge functions is merged then we should use it for this, as that would make it a lot easier to selectively target the edge function