Prepare various places to synchronous navigation commit

Once we start committing synchronously, some assumptions
about asynchronous flow will be broken. This patch updates
multilple places which can be updated separately (mostly tests).

WebFrameTest.ReplaceNavigationAfterHistoryNavigation is committing
a failing url, which does not happen in production anymore - we
commit an error page instead. It's functionality is covered
by RendererErrorPageTest, so removing.

WebFrameTest.BackDuringChildFrameReload has been migrated to
web_tests/http/tests/navigation/back-during-child-frame-reload.html.

WebFrameTest.LoadHistoryItemReload is only checking CacheMode
when committing navigation, which is useless since in production
this cache mode is handled on the browser and ignored in renderer.

See an example of synchronous commit for SubstitueData,
which requires all these changes:
https://chromium-review.googlesource.com/c/chromium/src/+/1389945.

Bug: 855189
Change-Id: Ib198d2373539113b4721ff5767da00794cb1a42f
Reviewed-on: https://chromium-review.googlesource.com/c/1392099
Commit-Queue: Dmitry Gozman <dgozman@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Tommy Li <tommycli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#620839}
21 files changed