Use a more thorough lookup when finding HistoryNodes to clone

In https://src.chromium.org/viewvc/blink?revision=163299&view=revision, I added a hack where, if we can't find the HistoryNode that allegedly navigated, append it where we think it should go. This doesn't work if the navigating HistoryNode is deep in the tree, and there's something wrong with one of its parents. Remove the hack, since it is treating the symptom rather than the underlying problem...

HistoryNode::cloneAndReplace() looks up based on frame id only, instead of frame id or frame name. That breaks the reload case, where the frame id of child frames won't be the same, but the unique name should be.

BUG=332725
TEST=http/tests/history/push-state-in-grandchild-after-reload.html

Review URL: https://codereview.chromium.org/139273006

git-svn-id: svn://svn.chromium.org/blink/trunk@165979 bbb929c8-8fbe-4397-9dbb-9b2b20218538