next.js

855ea3af - fix 'loading' segment not being copied into new CacheNode (#66538)

fix 'loading' segment not being copied into new CacheNode (#66538) When `router.refresh` or a server action creates a new `CacheNode` tree, we were erroneously not copying over the `loading` segment in the new tree. This would cause the subtree to be remounted as the loading segment switched from having a Suspense boundary to not having one. Fixes #66029 Fixes #66499