Revert of Prune connections based on network name.

Revert of Prune connections based on network name. (patchset #3 id:130001 of https://codereview.webrtc.org/2395243005/ )

Reason for revert:
Breaks upstream code.

Original issue's description:
> Prune connections based on network name.
> Previously we prune connections on the same network pointer.
> So if an IPv6 and an IPv4 network are on the same network interface, IPv4 connection won't be pruned even if an IPv6 connection with higher priority becomes writable.
>
> With this change, as long as one connection becomes writable, all connections  having lower priority with the same network name will be pruned.
>
> Also simplify the implementation.
>
> BUG=webrtc:6512
>
> Committed: https://crrev.com/aae2784c1fab9d1510393dec15d76caa574e2da8
> Cr-Commit-Position: refs/heads/master@{#14593}

TBR=skvlad@webrtc.org,honghaiz@webrtc.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=webrtc:6512
Committed: https://crrev.com/716978d075a6528ae77a2cef61753c27499d830f
Cr-Commit-Position: refs/heads/master@{#14601}

[sprang_webrtc, 2016-10-11 13:43:07]

The CQ bit was checked by sprang@webrtc.org

[sprang_webrtc, 2016-10-11 13:43:08]

Created Revert of Prune connections based on network name.

[commit-bot: I haz the power, 2016-10-11 13:43:21]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.webrtc.org/...

[commit-bot: I haz the power, 2016-10-11 13:43:31]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-10-11 13:43:40]

Description was changed from

==========
Revert of Prune connections based on network name. (patchset #3 id:130001 of
https://codereview.webrtc.org/2395243005/ )

Reason for revert:
Breaks upstream code.

Original issue's description:
> Prune connections based on network name.
> Previously we prune connections on the same network pointer.
> So if an IPv6 and an IPv4 network are on the same network interface, IPv4
connection won't be pruned even if an IPv6 connection with higher priority
becomes writable.
> 
> With this change, as long as one connection becomes writable, all connections 
having lower priority with the same network name will be pruned.
> 
> Also simplify the implementation.
> 
> BUG=webrtc:6512
> 
> Committed: https://crrev.com/aae2784c1fab9d1510393dec15d76caa574e2da8
> Cr-Commit-Position: refs/heads/master@{#14593}

TBR=skvlad@webrtc.org,honghaiz@webrtc.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=webrtc:6512
==========

to

==========
Revert of Prune connections based on network name. (patchset #3 id:130001 of
https://codereview.webrtc.org/2395243005/ )

Reason for revert:
Breaks upstream code.

Original issue's description:
> Prune connections based on network name.
> Previously we prune connections on the same network pointer.
> So if an IPv6 and an IPv4 network are on the same network interface, IPv4
connection won't be pruned even if an IPv6 connection with higher priority
becomes writable.
>
> With this change, as long as one connection becomes writable, all connections 
having lower priority with the same network name will be pruned.
>
> Also simplify the implementation.
>
> BUG=webrtc:6512
>
> Committed: https://crrev.com/aae2784c1fab9d1510393dec15d76caa574e2da8
> Cr-Commit-Position: refs/heads/master@{#14593}

TBR=skvlad@webrtc.org,honghaiz@webrtc.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=webrtc:6512

Committed: https://crrev.com/716978d075a6528ae77a2cef61753c27499d830f
Cr-Commit-Position: refs/heads/master@{#14601}
==========

[commit-bot: I haz the power, 2016-10-11 13:43:41]

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