Remove implicit conversions from scoped_refptr to T* in content/

Remove implicit conversions from scoped_refptr to T* in content/

This patch was generated by running the rewrite_scoped_refptr clang tool
on a Linux build.

BUG=110610
Committed: https://crrev.com/54c3719d6bd03e7f2a644b8ce611e68a67bc341f
Cr-Commit-Position: refs/heads/master@{#291986}

[dcheng, 2014-08-26 17:15:02]

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

[dcheng, 2014-08-26 17:15:03]

(This isn't actually all of content, this is the remainder after sharding out
most of the diffs in subdirectory chunks.)

Unfortunately, we can't make scoped_refptr testable until the conversion
operator has been removed. While it would be possible to disable the conversion
operator and make it testable in the same patch, the automated tool tries to
skip rewriting code where manual cleanups would be useful. This includes things
like:

// What if ReturnsScopedRefPtr() creates a new object internally?
if (ReturnsScopedRefPtr())

Foo* Bar() {
  const scoped_refptr<Foo>& f = ReturnsScopedRefPtr();
  return f;  // Does the return type need to be rewritten? Or is .get() safe?
}

Doing this in one patch would make catching some of these instances (in
particular, a boolean test on a temporary scoped_refptr) more difficult. As a
result, the work is being split into several steps:
Step 1: Rewrite all implicit conversions to be explicit (or rewrite the receiver
type to scoped_refptr<T>, if the tool believes the conversion to be unsafe).
Step 2: Once a platform compiles cleanly without the conversion operator, #ifdef
the conversion operator out.
Step 3: Make scoped_refptr testable on that platform.
Step 4: Remove unnecessary calls to .get().

[Avi (use Gerrit), 2014-08-26 19:38:53]

stampity stamp LGTM

[dcheng, 2014-08-26 19:40:01]

The CQ bit was checked by dcheng@chromium.org

[commit-bot: I haz the power, 2014-08-26 19:41:04]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/dcheng@chromium.org/504273002/1

[commit-bot: I haz the power, 2014-08-26 20:47:18]

FYI, CQ is re-trying this CL (attempt #1).
The failing builders are:
  win_chromium_x64_rel_swarming on tryserver.chromium.win
(http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_...)

[commit-bot: I haz the power, 2014-08-26 21:53:13]

Committed patchset #1 (1) as 48200442b474e21e104ec1df7636705a80fac3aa

[commit-bot: I haz the power, 2014-09-10 02:45:46]

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