redirect/3 doesn't match behaviour on the web

On the web, live navigation has the following behavior:

* `redirect` re-establish socket connection and re-mount the liveview
* `push_navigate` re-use existing socket connection and re-mount the liveview
* `push_patch` re-use existing socket connection and existing liveview (no `mount/3`, only handle_params)

However, on native our `redirect` event re-uses the existing socket connection rather than re-establishing it. I think this could be a potential security risk, or at the very least, doesn't match what developers will expect.