next.js

1b804c05 - fix: interception rewrites should support catch-all segments (#51787)

fix: interception rewrites should support catch-all segments (#51787) ### What? Interception route rewrites are not properly parsing catch-all segments, which leads to "missing parameter name" errors when passed to `pathToRegexp`. ### Why? The existing `toPathToRegexpPath` function ignores `...` and keeps it as part of the regexp path. This means `pathToRegexp` will attempt to handle `/foo/bar/:...baz` and `/foo/bar/:[...baz]` rather than `/foo/bar/:baz*` ### How? The regex used for matching the path was updated to support the dynamic optional segment, and then we special case catch-all segments Fixes #51784 ---------