GitLab

This CL adapts MixedContentChecker to do correct mixed content checks
for content that is mixed with respect to a remote frame. There are a
couple caveats/behavior changes:

- When mixed content is detected, the message logged to the console is
  changed slightly: when the mixed frame is remote, it prints the origin
  instead of the full URL.
- Subresources loaded with certificate errors are not yet correctly
  treated as mixed content when they are loaded in a remote HTTPS parent
  frame.
- FrameLoaderClient methods, for the most part, go to the client for the
  frame that loaded the resource, which is not necessarily the "mixed
  frame". This is weird, but in practice, the implementations of these
  FrameLoaderClient methods do not care which frame they are actually
  called on.
BUG=486936

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

Cr-Commit-Position: refs/heads/master@{#371534}