Speculatively revert "Stop reviving crashed RenderFrameHost. Get a new one instead."

Cause:
  Android webview is reaching a CHECK in the renderer process.
  See: https://crbug.com/1006814.

Plan:
 1) Revert speculatively.
 2) Cherry-pick to M78
 3) Reland later with:
    a) Some CHECK on the browser side to get useful StackTrace.
    b) Some Android webview specific tests.

Reverted CL:
-----------------------------------------------------------------------
Stop reviving crashed RenderFrameHost. Get a new one instead.

On same-site navigations, the browser reuses the current
RenderFrameHost, even if the current RenderFrameHost is crashed.

Instead of reviving the crashed one, we should get a new RenderFrameHost.

This can be seen as a small step in the direction of RenderDocument, which
intend to get a new RenderFrameHost every time, even if the previous
RenderFrameHost is not crashed.
https://docs.google.com/document/d/1C2VKkFRSc0kdmqjKan1G4NlNlxWZqE4Wam41FNMgnmA/edit

Bug: 981339
Change-Id: I17b11abe759906a7f360abeaa45f0bfc77e08768
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1688957
Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org>
Reviewed-by: Charlie Reis <creis@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
-----------------------------------------------------------------------

Bug: 1006814
Change-Id: Ic0b55d61739b5f64c46bf9326eb2fcd4fe03de0a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1848390
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#704567}
6 files changed