Replace missing call to RenderFrameHostImpl::Init().

Replace missing call to RenderFrameHostImpl::Init().

This only affects renderer-created windows.  It resumes blocked requests
for the RenderFrameHost, which is currently a no-op (until we start routing
network requests through RenderFrameHost rather than RenderViewHost).

BUG=414947
TEST=RFH's requests unblocked after window.open.  (No behavior change.)

Committed: https://crrev.com/82dd6af930a59e47c31ef58dbd3644014dde3589
Cr-Commit-Position: refs/heads/master@{#295286}

[Charlie Reis, 2014-09-16 23:19:07]

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

[Charlie Reis, 2014-09-16 23:24:59]

I haven't found a good way to test this, since it currently has no observable
effect on navigation (until we use frame routing IDs for network requests), and
the blocked request state is on the IO thread in ResourceDispatcherHost.  I've
confirmed manually that the RFH is no longer left in the blocked_loaders_map_.

It may be sufficient to rely on existing window.open() tests for this, since
those would have broken once we start using frame routing IDs for network
requests.

[nasko, 2014-09-17 06:46:21]

lgtm

[Charlie Reis, 2014-09-17 15:58:50]

The CQ bit was checked by creis@chromium.org

[commit-bot: I haz the power, 2014-09-17 15:59:01]

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

[commit-bot: I haz the power, 2014-09-17 16:30:52]

Committed patchset #1 (id:1) as 33bfbd907857b21483cd4f629fc2b6fc9d6380ec

[commit-bot: I haz the power, 2014-09-17 16:31:25]

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