[M53 cherry-pick] Migrate ArcUserDataService into ArcAuthService.

Migrate ArcUserDataService into ArcAuthService.

There are race problems around data removing.
One of the cause is that state management is done in
ArcAuthService and ArcUserDataService separately.

This CL migrates ArcUserDataService into ArcAuthService
so that we can remove the data when necessary.

BUG=633258, 636218
TEST=Ran manually.
     - "Enable -> ARC boot wait -> Disable" triggers data removal after
       ARC stop.
     - "Enable -> Disable before ARC boot" triggers immediate data
       removal.
     - "Enable -> ARC boot wait -> Kill ARC instance" does not trigger
       data removal.
R=dspaid@chromium.org, lhchavez@chromium.org
TBR=khmel@chromium.org, lhchavez@chromium.org, stevenjb@chromium.org

Review-Url: https://codereview.chromium.org/2209173002
Cr-Commit-Position: refs/heads/master@{#411923}
(cherry picked from commit 6d95ad318e992261c45f5a88a0a599663a6d66ae)

Committed: https://chromium.googlesource.com/chromium/src/+/d7ca35a59c7bd8c7ddd78d7682458e48e6b4e934

[hidehiko, 2016-08-17 09:47:37]

Description was changed from

==========
Migrate ArcUserDataService into ArcAuthService.

There are race problems around data removing.
One of the cause is that state management is done in
ArcAuthService and ArcUserDataService separately.

This CL migrates ArcUserDataService into ArcAuthService
so that we can remove the data when necessary.

BUG=633258
TEST=Ran manually.
     - "Enable -> ARC boot wait -> Disable" triggers data removal after
       ARC stop.
     - "Enable -> Disable before ARC boot" triggers immediate data
       removal.
     - "Enable -> ARC boot wait -> Kill ARC instance" does not trigger
       data removal.

Review-Url: https://codereview.chromium.org/2209173002
Cr-Commit-Position: refs/heads/master@{#411923}
(cherry picked from commit 6d95ad318e992261c45f5a88a0a599663a6d66ae)
==========

to

==========
Migrate ArcUserDataService into ArcAuthService.

There are race problems around data removing.
One of the cause is that state management is done in
ArcAuthService and ArcUserDataService separately.

This CL migrates ArcUserDataService into ArcAuthService
so that we can remove the data when necessary.

BUG=633258, 636218
TEST=Ran manually.
     - "Enable -> ARC boot wait -> Disable" triggers data removal after
       ARC stop.
     - "Enable -> Disable before ARC boot" triggers immediate data
       removal.
     - "Enable -> ARC boot wait -> Kill ARC instance" does not trigger
       data removal.

Review-Url: https://codereview.chromium.org/2209173002
Cr-Commit-Position: refs/heads/master@{#411923}
(cherry picked from commit 6d95ad318e992261c45f5a88a0a599663a6d66ae)
==========

[hidehiko, 2016-08-17 09:49:19]

Description was changed from

==========
Migrate ArcUserDataService into ArcAuthService.

There are race problems around data removing.
One of the cause is that state management is done in
ArcAuthService and ArcUserDataService separately.

This CL migrates ArcUserDataService into ArcAuthService
so that we can remove the data when necessary.

BUG=633258, 636218
TEST=Ran manually.
     - "Enable -> ARC boot wait -> Disable" triggers data removal after
       ARC stop.
     - "Enable -> Disable before ARC boot" triggers immediate data
       removal.
     - "Enable -> ARC boot wait -> Kill ARC instance" does not trigger
       data removal.

Review-Url: https://codereview.chromium.org/2209173002
Cr-Commit-Position: refs/heads/master@{#411923}
(cherry picked from commit 6d95ad318e992261c45f5a88a0a599663a6d66ae)
==========

to

==========
Migrate ArcUserDataService into ArcAuthService.

There are race problems around data removing.
One of the cause is that state management is done in
ArcAuthService and ArcUserDataService separately.

This CL migrates ArcUserDataService into ArcAuthService
so that we can remove the data when necessary.

BUG=633258, 636218
TEST=Ran manually.
     - "Enable -> ARC boot wait -> Disable" triggers data removal after
       ARC stop.
     - "Enable -> Disable before ARC boot" triggers immediate data
       removal.
     - "Enable -> ARC boot wait -> Kill ARC instance" does not trigger
       data removal.
TBR=lhchavez@chromium.org, stevenjb@chromium.org, khmel@chromium.org

Review-Url: https://codereview.chromium.org/2209173002
Cr-Commit-Position: refs/heads/master@{#411923}
(cherry picked from commit 6d95ad318e992261c45f5a88a0a599663a6d66ae)
==========

[hidehiko, 2016-08-17 09:49:20]

hidehiko@chromium.org changed reviewers:
+ dspaid@chromium.org, khmel@chromium.org, lhchavez@chromium.org,
stevenjb@chromium.org

[hidehiko, 2016-08-17 09:52:23]

This is M53 cherry pick. 

https://codereview.chromium.org/2248353002/diff/1/chrome/browser/chromeos/arc...
L460 is the only conflict line.

Dan, PTAL for that part?

TBRing other original reviewers.

Note: added the BUG for M53 merge approval.

[Luis Héctor Chávez, 2016-08-17 15:20:37]

rs-lgtm

[dspaid, 2016-08-17 22:58:12]

lgtm

[hidehiko, 2016-08-18 04:20:35]

Thank you for review. Landing.
TBR=stevenjb, kheml (no diff from original CL).

[hidehiko, 2016-08-18 04:25:37]

Description was changed from

==========
Migrate ArcUserDataService into ArcAuthService.

There are race problems around data removing.
One of the cause is that state management is done in
ArcAuthService and ArcUserDataService separately.

This CL migrates ArcUserDataService into ArcAuthService
so that we can remove the data when necessary.

BUG=633258, 636218
TEST=Ran manually.
     - "Enable -> ARC boot wait -> Disable" triggers data removal after
       ARC stop.
     - "Enable -> Disable before ARC boot" triggers immediate data
       removal.
     - "Enable -> ARC boot wait -> Kill ARC instance" does not trigger
       data removal.
TBR=lhchavez@chromium.org, stevenjb@chromium.org, khmel@chromium.org

Review-Url: https://codereview.chromium.org/2209173002
Cr-Commit-Position: refs/heads/master@{#411923}
(cherry picked from commit 6d95ad318e992261c45f5a88a0a599663a6d66ae)
==========

to

==========
Migrate ArcUserDataService into ArcAuthService.

There are race problems around data removing.
One of the cause is that state management is done in
ArcAuthService and ArcUserDataService separately.

This CL migrates ArcUserDataService into ArcAuthService
so that we can remove the data when necessary.

BUG=633258, 636218
TEST=Ran manually.
     - "Enable -> ARC boot wait -> Disable" triggers data removal after
       ARC stop.
     - "Enable -> Disable before ARC boot" triggers immediate data
       removal.
     - "Enable -> ARC boot wait -> Kill ARC instance" does not trigger
       data removal.
R=dspaid@chromium.org, lhchavez@chromium.org
TBR=khmel@chromium.org, lhchavez@chromium.org, stevenjb@chromium.org

Review-Url: https://codereview.chromium.org/2209173002
Cr-Commit-Position: refs/heads/master@{#411923}
(cherry picked from commit 6d95ad318e992261c45f5a88a0a599663a6d66ae)

Committed:
https://chromium.googlesource.com/chromium/src/+/d7ca35a59c7bd8c7ddd78d768245...
==========

[hidehiko, 2016-08-18 04:25:39]

Committed patchset #1 (id:1) manually as
d7ca35a59c7bd8c7ddd78d7682458e48e6b4e934.

[khmel, 2016-08-18 22:20:03]

A revert of this CL (patchset #1 id:1) has been created in
https://codereview.chromium.org/2255673004/ by khmel@chromium.org.

The reason for reverting is: Compilation problem:

../../chrome/browser/chromeos/arc/arc_auth_service.cc:244:34: error: no member
named 'stopped' in 'arc::ArcBridgeService'.