### What?
Parallel routes build in a weird and render in a weird way.
To render next.js always uses the last parallel route (alphabetically I
think) as that's most likely to be the root.
Building works in the opposite order, it goes from the first to the
last.
This is fine for the first render, but after that the renderer will only
check if the file for the last parallel route has a bundle on disk and
never request it to be updated.
1. match on routes
2. build match
3. check if the last parallel route bundle exists on disk
- if it doesn't so go back to step 2 with the next match
- the actual match gets thrown away
4. render with the bundle for the last parallel route
The condition in step 3 will always be true after an update, because it
was built for a previous request
To fix this, turbopack will now emit all parallel routes that match a
path every time one of them gets requested.
Closes PACK-3078
Fixes#65836
4df48390db