fix(astro): Fixes prerender conflicts of lower-priority routes

[Fryuni]

Changes

• Fixes Adapters not following the route priority ordering after build #11266
• The routes are sorted by priority and built, but the adapters serve all pre-rendered pages in front of the applications.
• Prerendered routes that would conflict with a higher priority SSR route are now skipped, just as they are for other higher-priority pre-rendered routes.
• The dev server was already following the route priority order since it matches based on the route list. Only prod builds incorrectly placed lower-priority routes in front of higher-priority routes.

Testing

A new lower-priority route (with a rest parameter) was added to the ssr-prerender test suite that conflicts with the pre-rendered /static route and the SSR /not-prerendered route. The new route must be skipped in both cases, resulting in:

• A prerendered /static path with the contents of the /static route
• No /not-prerendered being prerendered

Docs

The new behavior matches what is already documented.

[changeset-bot]

🦋 Changeset detected

Latest commit: 23767b5

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[Fryuni]

Whoops, I didn't consider the fallback routes. Back to the board

[ematipico]

Whoops, I didn't consider the fallback routes. Back to the board

Fallback routes should be really simple to handle. However, maybe we should refactor them.

At the moment they contain copies of what we already have inside RouteData[]. Maybe we should, instead, just save the index of those routes.

[ematipico]

@Fryuni any updates?