Fix RSC Redirects

[blittle]

Description

Fix RSC Redirects. Resolves #947

Additional context

Fix server redirects to work properly with RSC responses. For example, the redirect component within the starter template changes:

export default function Redirect({response}) {
-  response.redirect('/products/snowboard');
-  return <div>This page is redirected</div>;
+  return response.redirect('/products/snowboard');
}

This server component is executed two ways:

1. When an app directly loads the redirect route, the server will render a 300 redirect with the proper location header.
2. The app is already loaded, but the user navigates to the redirected route. We cannot 300 respond in this scenario, instead response.redirect(...) returns a component which will redirect on the client.

The redirect e2e test has been modified to cover this scenario.

[jplhomer]

Nice. This is way more elegant than I assumed it would be.

[blittle]

@mcvinci FYI there's some documentation changes in here

[mcvinci]

Docs changes look good! Thanks, @blittle!

[frandiox]

Thanks Bret! Very simple and elegant solution.

I've noticed there are two Redirect.client.xyz.js files emitted when building the client, and it seems to be related to including Redirect component in ServerComponentResponse.server.js. I've no idea why because that file should not affect the client at all...
I think it is not a big issue anyway so we can merge this. Perhaps things will be clearer once we extract client stuff into hydrogen-ui.

[michenly]

should this be window.location.replace instead so its truly a redirect?