avoid extra round trip for action redirect?

[hi-ogawa]

Currently, action redirect is propagated back to client, then let it handle client side navigation again. It might be possible to skip this roundtrip by processing redirect internally and return flight render of new path.
(Also check what Next.js does.)

this part is fixed in another way

(see #530)

This also avoids confusing issues when redirecting after resource deletion like in this demo:

https://github.com/hi-ogawa/rsc-on-vite/blob/89303058e0b46799da581b42fdf5797aa52faa8a/remix-tutorial/src/routes/_action.ts#L13-L18

  // TODO
  // action response stream renders `src/routes/contacts/[contactId]/page.tsx`
  // but contact doesn't exists anymore and server component throws,
  // which makes this redirect error to not caught by client
  // when users don't have custom error page
  throw redirect("/");