Handle hosted apps consistently in --isolate-extensions.

Handle hosted apps consistently in --isolate-extensions.

Ultimately, we want hosted apps not to be isolated by --isolate-extensions.
However, the current implementation was excluding them from isolation
by accident, because we weren't looking up the effective url. As a result,
we were inconstent: app.com(web.com) was 2 processes, but web.com(app.com)
was one process.

This CL fixes the inconsistency, and fixes a test TODO where we noticed the problem.

TBR=jam@chromium.org
BUG=535073
TEST=browser_tests with --isolate-extensions (the bots don't run this yet)

Committed: https://crrev.com/8a1a0feb26645f14fe00618493d9364b004eea7a
Cr-Commit-Position: refs/heads/master@{#351829}

[ncarter (slow), 2015-09-30 22:32:27]

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

[Charlie Reis, 2015-09-30 23:01:01]

LGTM.  (While in one sense we're moving backwards and don't want to isolate
hosted apps in either case, I totally agree with fixing this bug first.)

[ncarter (slow), 2015-10-01 16:43:45]

nick@chromium.org changed reviewers:
+ jam@chromium.org

[ncarter (slow), 2015-10-01 16:44:11]

TBRing jam (one line test expectation fix in chrome/)

[ncarter (slow), 2015-10-01 16:44:17]

The CQ bit was checked by nick@chromium.org

[commit-bot: I haz the power, 2015-10-01 16:45:28]

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

[commit-bot: I haz the power, 2015-10-01 17:14:20]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-10-01 17:15:17]

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

[jam, 2015-10-02 17:04:14]

On 2015/10/01 16:44:11, ncarter wrote:
> TBRing jam (one line test expectation fix in chrome/)

lgtm

you should add the site isolation folks as owners for that file