Remove ManifestFetchData parameter from SafeManifestParser

Remove ManifestFetchData parameter from SafeManifestParser

All it was doing with it is passing it through to its completion
callback (apart from 2 VLOG statements). This CL changes to binding it
to the callback directly with the base::Bind call.

Also rename UpdateCallback to ResultsCallback, because that seemed like
a better name to me. And run our autoformatting thing As Required By Law.

BUG=458373
Committed: https://crrev.com/d71a7a6b1d878a5c0077863e03b6f12eabaee2b7
Cr-Commit-Position: refs/heads/master@{#316342}

[asargent_no_longer_on_chrome, 2015-02-13 01:04:11]

asargent@chromium.org changed reviewers:
+ mek@chromium.org

[asargent_no_longer_on_chrome, 2015-02-13 01:04:11]

This is a small chunk of refactoring I broke out of a larger CL I'm working on.
(ie it's not *just* code churn, but will help me accomplish reuse of
SafeManifestParser code in a situation where I don't have a ManifestFetchData)

[Marijn Kruisselbrink, 2015-02-13 17:16:57]

lgtm

[asargent_no_longer_on_chrome, 2015-02-13 17:25:10]

The CQ bit was checked by asargent@chromium.org

[commit-bot: I haz the power, 2015-02-13 17:26:36]

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

[commit-bot: I haz the power, 2015-02-13 17:38:11]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-02-13 17:38:12]

Try jobs failed on following builders:
  linux_chromium_gn_chromeos_rel on tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[asargent_no_longer_on_chrome, 2015-02-13 17:47:59]

New patchsets have been uploaded after l-g-t-m from mek@chromium.org

[asargent_no_longer_on_chrome, 2015-02-13 17:48:13]

The CQ bit was checked by asargent@chromium.org

[asargent_no_longer_on_chrome, 2015-02-13 17:48:55]

Missed a conversation from const ref to const pointer in a unit test file ; new
version fixes that

[commit-bot: I haz the power, 2015-02-13 17:49:18]

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

[commit-bot: I haz the power, 2015-02-13 18:53:48]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-02-13 18:53:48]

Try jobs failed on following builders:
  linux_chromium_chromeos_rel_ng on tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[asargent_no_longer_on_chrome, 2015-02-13 19:16:50]

new version uploaded which moves VLOG statement above return to eliminate
unreachable code error

[asargent_no_longer_on_chrome, 2015-02-13 23:45:26]

The CQ bit was checked by asargent@chromium.org

[commit-bot: I haz the power, 2015-02-13 23:47:08]

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

[commit-bot: I haz the power, 2015-02-14 00:32:08]

Committed patchset #4 (id:60001)

[commit-bot: I haz the power, 2015-02-14 00:32:42]

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