Revert of [BackgroundSync] Trigger Background Sync events when Chrome is backgrounded on Android

Revert of [BackgroundSync] Trigger Background Sync events when Chrome is backgrounded on Android (patchset #20 id:400001 of https://codereview.chromium.org/1294603003/ )

Reason for revert:
This patch breaks Android System WebView embedding, by assuming that ACCESS_NETWORK_STATE is available in all cases.

NetworkChangeNotifierAutoDetect should not be created automatically by a WebView. Need to fix this before relanding this patch.

Crashing bug report: https://crbug.com/537294

Original issue's description:
> [BackgroundSync] Trigger Background Sync events when Chrome is backgrounded on Android
>
> BUG=511129
>
> Committed: https://crrev.com/a5fb97d6fb9c3831994aadebea4664e2acc3c356
> Cr-Commit-Position: refs/heads/master@{#351093}

TBR=jochen@chromium.org,jkarlin@chromium.org,yfriedman@chromium.org,mmenke@chromium.org
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=511129
Committed: https://crrev.com/c532c674b657426cb733c2b735bbf5741bcbea48
Cr-Commit-Position: refs/heads/master@{#351381}

[iclelland, 2015-09-29 19:44:37]

Created Revert of [BackgroundSync] Trigger Background Sync events when Chrome is
backgrounded on Android

[commit-bot: I haz the power, 2015-09-29 19:45:20]

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

[commit-bot: I haz the power, 2015-09-29 19:45:21]

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

[commit-bot: I haz the power, 2015-09-29 19:45:22]

No L-G-T-M from a valid reviewer yet. Only full committers are accepted.
Even if an L-G-T-M may have been provided, it was from a non-committer,
_not_ a full super star committer.
See http://www.chromium.org/getting-involved/become-a-committer
Note that this has nothing to do with OWNERS files.

[boliu, 2015-09-29 19:46:51]

commiter stamp lgtm

[boliu, 2015-09-29 19:47:55]

Can you include crbug.com/537294 too?

[iclelland, 2015-09-29 19:51:33]

On 2015/09/29 19:47:55, boliu wrote:
> Can you include crbug.com/537294 too?

Do you mean in the description?

[iclelland, 2015-09-29 19:52:38]

On 2015/09/29 19:51:33, iclelland wrote:
> On 2015/09/29 19:47:55, boliu wrote:
> > Can you include crbug.com/537294 too?
> 
> Do you mean in the description?

(It was marked restricted, so I wasn't sure if it was appropriate to include in
the public commit history)

[iclelland, 2015-09-29 19:55:44]

The CQ bit was checked by iclelland@chromium.org

[commit-bot: I haz the power, 2015-09-29 19:56:25]

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

[commit-bot: I haz the power, 2015-09-29 19:58:36]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-09-29 20:00:03]

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

[Yaron, 2015-09-29 21:18:24]

On 2015/09/29 20:00:03, commit-bot: I haz the power wrote:
> Patchset 1 (id:??) landed as
> https://crrev.com/c532c674b657426cb733c2b735bbf5741bcbea48
> Cr-Commit-Position: refs/heads/master@{#351381}

It's fine to reference restricted bugs. The link will fail if someone doesn't
have access but it's still helpful to connect for those that do. :)