Use OnceCallback on Mojo interfaces in //components/chrome_cleaner

Use OnceCallback on Mojo interfaces in //components/chrome_cleaner
    
This CL flips `use_once_calback` flag on the Mojo code generator, and
fixes all compile errors after it. After this CL, Mojo interfaces in
//components/chrome_cleaner starts using base::OnceCallback instead of
base::Callback on its return value handling.

The migration recipe was:
 - Convert pass-by-ref callback objects to pass-by-value.
 - Use std::move() to forward it to other consumer, or to invoke it
   with Callback::Run().
 - Handle wherever copies are required manually.
 - Check if the conversion doesn't change the semantics. As the transfer
   and invocation clobber the callback object, care about use-after-move.
   It's considered safe to consume almost scoped-out callback.

BUG=714018
Review-Url: https://codereview.chromium.org/2867723002
Cr-Commit-Position: refs/heads/master@{#470322}
Committed: https://chromium.googlesource.com/chromium/src/+/5fa4456aa172ddb1dd6bb47036786bb94375fd62

[tzik, 2017-05-08 07:56:14]

The CQ bit was checked by tzik@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-05-08 07:56:48]

Dry run: CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-05-08 08:54:08]

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

[commit-bot: I haz the power, 2017-05-08 08:54:10]

Dry run: Try jobs failed on following builders:
  win_chromium_compile_dbg_ng on master.tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_comp...)

[tzik, 2017-05-09 07:23:59]

The CQ bit was checked by tzik@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-05-09 07:24:32]

Dry run: CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[tzik, 2017-05-09 07:24:40]

Description was changed from

==========
Use OnceCallback on Mojo interfaces in //components/chrome_cleaner
==========

to

==========
Use OnceCallback on Mojo interfaces in //components/chrome_cleaner
    
This CL flips `use_once_calback` flag on the Mojo code generator, and
fixes all compile errors after it. After this CL, Mojo interfaces in
//components/chrome_cleaner starts using base::OnceCallback instead of
base::Callback on its return value handling.

The migration recipe was:
 - Convert pass-by-ref callback objects to pass-by-value.
 - Use std::move() to forward it to other consumer, or to invoke it
   with Callback::Run().
 - Handle wherever copies are required manually.
 - Check if the conversion doesn't change the semantics. As the transfer
   and invocation clobber the callback object, care about use-after-move.
   It's considered safe to consume almost scoped-out callback.

BUG=714018
==========

[tzik, 2017-05-09 07:25:21]

tzik@chromium.org changed reviewers:
+ robertshield@chromium.org

[tzik, 2017-05-09 09:10:18]

PTAL

[commit-bot: I haz the power, 2017-05-09 11:22:34]

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

[commit-bot: I haz the power, 2017-05-09 11:22:35]

Dry run: This issue passed the CQ dry run.

[robertshield, 2017-05-09 13:29:07]

lgtm

[tzik, 2017-05-09 14:15:09]

The CQ bit was checked by tzik@chromium.org

[commit-bot: I haz the power, 2017-05-09 14:15:24]

CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-05-09 14:23:42]

CQ is committing da patch.

Bot data: {"patchset_id": 20001, "attempt_start_ts": 1494339309540100,
"parent_rev": "9a17d7afe9e954902eb5d339258f3ea041ad15ec", "commit_rev":
"5fa4456aa172ddb1dd6bb47036786bb94375fd62"}

[commit-bot: I haz the power, 2017-05-09 14:23:52]

Description was changed from

==========
Use OnceCallback on Mojo interfaces in //components/chrome_cleaner
    
This CL flips `use_once_calback` flag on the Mojo code generator, and
fixes all compile errors after it. After this CL, Mojo interfaces in
//components/chrome_cleaner starts using base::OnceCallback instead of
base::Callback on its return value handling.

The migration recipe was:
 - Convert pass-by-ref callback objects to pass-by-value.
 - Use std::move() to forward it to other consumer, or to invoke it
   with Callback::Run().
 - Handle wherever copies are required manually.
 - Check if the conversion doesn't change the semantics. As the transfer
   and invocation clobber the callback object, care about use-after-move.
   It's considered safe to consume almost scoped-out callback.

BUG=714018
==========

to

==========
Use OnceCallback on Mojo interfaces in //components/chrome_cleaner
    
This CL flips `use_once_calback` flag on the Mojo code generator, and
fixes all compile errors after it. After this CL, Mojo interfaces in
//components/chrome_cleaner starts using base::OnceCallback instead of
base::Callback on its return value handling.

The migration recipe was:
 - Convert pass-by-ref callback objects to pass-by-value.
 - Use std::move() to forward it to other consumer, or to invoke it
   with Callback::Run().
 - Handle wherever copies are required manually.
 - Check if the conversion doesn't change the semantics. As the transfer
   and invocation clobber the callback object, care about use-after-move.
   It's considered safe to consume almost scoped-out callback.

BUG=714018

Review-Url: https://codereview.chromium.org/2867723002
Cr-Commit-Position: refs/heads/master@{#470322}
Committed:
https://chromium.googlesource.com/chromium/src/+/5fa4456aa172ddb1dd6bb4703678...
==========

[commit-bot: I haz the power, 2017-05-09 14:23:54]

Committed patchset #2 (id:20001) as
https://chromium.googlesource.com/chromium/src/+/5fa4456aa172ddb1dd6bb4703678...