next.js

93eb32d9 - Remove default fallback behavior when route group is missing a default (#62370)

Remove default fallback behavior when route group is missing a default (#62370) This test case was added in #59752, but this doesn't seem like the correct behavior. The original PR was intended to be smart about resolving `/default.tsx` to a route group default (e.g. `/(foo)/default.tsx`) when one wasn't specified. But since the route group is creating a new hierarchy in the tree and defines its own layout, if the route group layout doesn't specify a default, then the not found behavior seems correct. To fix unexpected not-found behavior in this case, you should specify a default at the same level as the layout where the missing slot(s) might be rendered. Closes NEXT-2565