Fixing the super-long delay when GCMAccountTracker posts a task

Fixing the super-long delay when GCMAccountTracker posts a task

* In order to sort out dependencies between initialization of components, I am doing work only when I have a valid GCM connection going (this means all the infrastructure is up and running).
* I am also making sure that time to next token reporting is always between 0 and 12 hours.

BUG=453018
Committed: https://crrev.com/702e92edc36eecb6d77d97947929c2e31775bd71
Cr-Commit-Position: refs/heads/master@{#313754}

[fgorski, 2015-01-28 23:05:10]

fgorski@chromium.org changed reviewers:
+ miu@chromium.org

[miu, 2015-01-28 23:20:14]

lgtm, but didn't you also want to fix the code in
GCMStoreImpl::Backend::LoadLastTokenFetchTime(), where base::StringToInt64() is
called?

[fgorski, 2015-01-28 23:57:30]

On 2015/01/28 23:20:14, miu wrote:
> lgtm, but didn't you also want to fix the code in
> GCMStoreImpl::Backend::LoadLastTokenFetchTime(), where base::StringToInt64()
is
> called?

Covered by https://codereview.chromium.org/884783003/

[fgorski, 2015-01-29 18:39:06]

The CQ bit was checked by fgorski@chromium.org

[commit-bot: I haz the power, 2015-01-29 18:39:47]

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

[commit-bot: I haz the power, 2015-01-29 19:22:32]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2015-01-29 19:23:42]

Patchset 2 (id:??) landed as
https://crrev.com/702e92edc36eecb6d77d97947929c2e31775bd71
Cr-Commit-Position: refs/heads/master@{#313754}