Pass explicitly the frame to HistoryController::GoToEntry

Pass explicitly the frame to HistoryController::GoToEntry

When doing a session history navigation cross-process in a frame which
already has a proxy, the proxy is replaced by a new real frame. In this
case, HistoryController doesn't know about the new frame it needs to
interact with, so this CL adds it as an explicit parameter in GoToEntry.

This scenario becomes possible once we stop using swapped out frames
for navigation in regular Chrome.

BUG=357747
Committed: https://crrev.com/ea32ae1fb0617e83b96b965ba10a31df38aa3269
Cr-Commit-Position: refs/heads/master@{#336370}

[nasko, 2015-06-26 14:51:39]

nasko@chromium.org changed reviewers:
+ avi@chromium.org

[nasko, 2015-06-26 14:51:40]

Hey Avi,
Can you review this CL for me? It is a split from the bigger swapped out removal
CL. Feel free to CQ it if it looks good.
Thanks in advance!
Nasko

[Avi (use Gerrit), 2015-06-26 15:10:51]

The CQ bit was checked by avi@chromium.org

[Avi (use Gerrit), 2015-06-26 15:10:52]

lgtm

Still looks good to me from last time.

[commit-bot: I haz the power, 2015-06-26 15:11:41]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1212363002/1

[commit-bot: I haz the power, 2015-06-26 15:16:11]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-06-26 15:17:11]

Patchset 1 (id:??) landed as
https://crrev.com/ea32ae1fb0617e83b96b965ba10a31df38aa3269
Cr-Commit-Position: refs/heads/master@{#336370}