next.js

b7d438cf - Invalidate prefetch cache when a tag or path has been revalidated on the server (#50848)

Invalidate prefetch cache when a tag or path has been revalidated on the server (#50848) This makes sure that if `revalidateTag` is called in a Server Action, the client router cache and prefetch cache are invalidated correctly so following navigations won't reuse the cache that might hold stale data. Similar case for `revalidatePath`. I left a TODO where we can't just invalidate the subtree under the revalidate paths because of current implementation limitations. To ensure correctness, we just do the same as `revalidateTag`.