[next] Fix _next/data resolving priority for dynamic routes

[ijjk]

Related Issues

This ensures we include all dynamic routes as data routes when we are resolving data routes with middleware. Without this we can incorrectly resolve a more generic dynamic route that has a data route before matching a more specific dynamic route that doesn't have a data route (e.g. an automatic static optimized page).

Fixes: slack thread

📋 Checklist

Tests

• The code changed/added as part of this PR has been covered with tests
• All tests pass locally with yarn test-unit

Code Review

• This PR has a concise title and thorough description useful to a reviewer
• Issue from task tracker has a link to this PR