allow route matching to find the route even if a dynamic page exists …

[enex]

…with a potentially matching segment

If a user has an app dreictory that looks something like this:

[something]/page.tsx websocket/route.ts

next-ws would not have detected websocket as viable route and would have faild to allow the websocket connection