Revert of Fix backwards WebRTC-in-Chromium override and expose Chromium logging setup

Revert of Fix backwards WebRTC-in-Chromium override and expose Chromium logging setup (patchset #4 id:60001 of https://codereview.chromium.org/1982643002/ )

Reason for revert:
The signature change for LogToDebug broke JNI on Android.

Original issue's description:
> Fix backwards WebRTC-in-Chromium override, and expose a way for WebRTC code to initialise the Chromium logging system.
>
> BUG=561667
>
> Committed: https://crrev.com/85d72ea76ae71e4b9d71d990e67c9d6b3cc1d145
> Cr-Commit-Position: refs/heads/master@{#394384}

TBR=grunell@chromium.org,tommi@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=561667
Committed: https://crrev.com/422e802b3862f7a1c1827fe735eb67a8329b6ca5
Cr-Commit-Position: refs/heads/master@{#394765}

[katrielc, 2016-05-19 13:12:00]

Created Revert of Fix backwards WebRTC-in-Chromium override and expose Chromium
logging setup

[commit-bot: I haz the power, 2016-05-19 13:12:15]

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

[commit-bot: I haz the power, 2016-05-19 13:12:15]

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

[commit-bot: I haz the power, 2016-05-19 13:12:16]

No L-G-T-M from a valid reviewer yet. 
CQ run can only be started by full committers or once the patch has
received an L-G-T-M from a full committer.
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.

[phoglund_chromium, 2016-05-19 13:15:40]

phoglund@chromium.org changed reviewers:
+ phoglund@chromium.org

[phoglund_chromium, 2016-05-19 13:15:40]

lgtm

lgtm

[katrielc, 2016-05-19 13:15:59]

The CQ bit was checked by katrielc@chromium.org

[commit-bot: I haz the power, 2016-05-19 13:16:13]

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

[commit-bot: I haz the power, 2016-05-19 14:34:09]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-05-19 14:35:57]

Description was changed from

==========
Revert of Fix backwards WebRTC-in-Chromium override and expose Chromium logging
setup (patchset #4 id:60001 of https://codereview.chromium.org/1982643002/ )

Reason for revert:
The signature change for LogToDebug broke JNI on Android.

Original issue's description:
> Fix backwards WebRTC-in-Chromium override, and expose a way for WebRTC code to
initialise the Chromium logging system.
> 
> BUG=561667
> 
> Committed: https://crrev.com/85d72ea76ae71e4b9d71d990e67c9d6b3cc1d145
> Cr-Commit-Position: refs/heads/master@{#394384}

TBR=grunell@chromium.org,tommi@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=561667
==========

to

==========
Revert of Fix backwards WebRTC-in-Chromium override and expose Chromium logging
setup (patchset #4 id:60001 of https://codereview.chromium.org/1982643002/ )

Reason for revert:
The signature change for LogToDebug broke JNI on Android.

Original issue's description:
> Fix backwards WebRTC-in-Chromium override, and expose a way for WebRTC code to
initialise the Chromium logging system.
>
> BUG=561667
>
> Committed: https://crrev.com/85d72ea76ae71e4b9d71d990e67c9d6b3cc1d145
> Cr-Commit-Position: refs/heads/master@{#394384}

TBR=grunell@chromium.org,tommi@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=561667

Committed: https://crrev.com/422e802b3862f7a1c1827fe735eb67a8329b6ca5
Cr-Commit-Position: refs/heads/master@{#394765}
==========

[commit-bot: I haz the power, 2016-05-19 14:35:57]

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