Revert of Refactor webrtc/modules/video_processing for GN check

Revert of Refactor webrtc/modules/video_processing for GN check (patchset #3 id:40001 of https://codereview.webrtc.org/2595543002/ )

Reason for revert:
This CL broke some buildbots. I will investigate it later.

Original issue's description:
> Refactor webrtc/modules/video_processing for GN check
> 
> This moves some GN check configurations out of .gn to individual
> targets.
> 
> The now checked target is:
> "//webrtc/modules/video_processing/*"
> 
> BUG=webrtc:6828
> NOTRY=True
> 
> Review-Url: https://codereview.webrtc.org/2595543002
> Cr-Commit-Position: refs/heads/master@{#15732}
> Committed: https://chromium.googlesource.com/external/webrtc/+/00a810b844b2393b64f7e36ce1524dd9e3dccb4b

TBR=kjellander@webrtc.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=webrtc:6828
Review-Url: https://codereview.webrtc.org/2594973002
Cr-Commit-Position: refs/heads/master@{#15733}
Committed: https://chromium.googlesource.com/external/webrtc/+/d39e16ac300d7947d22b953898aaef073e553ad3

[mbonadei, 2016-12-21 10:18:49]

The CQ bit was checked by mbonadei@webrtc.org

[mbonadei, 2016-12-21 10:18:49]

Created Revert of Refactor webrtc/modules/video_processing for GN check

[commit-bot: I haz the power, 2016-12-21 10:18:52]

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-12-21 10:18:55]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1482315529355240, "parent_rev":
"00a810b844b2393b64f7e36ce1524dd9e3dccb4b", "commit_rev":
"d39e16ac300d7947d22b953898aaef073e553ad3"}

[commit-bot: I haz the power, 2016-12-21 10:18:57]

Description was changed from

==========
Revert of Refactor webrtc/modules/video_processing for GN check (patchset #3
id:40001 of https://codereview.webrtc.org/2595543002/ )

Reason for revert:
This CL broke some buildbots. I will investigate it later.

Original issue's description:
> Refactor webrtc/modules/video_processing for GN check
> 
> This moves some GN check configurations out of .gn to individual
> targets.
> 
> The now checked target is:
> "//webrtc/modules/video_processing/*"
> 
> BUG=webrtc:6828
> NOTRY=True
> 
> Review-Url: https://codereview.webrtc.org/2595543002
> Cr-Commit-Position: refs/heads/master@{#15732}
> Committed:
https://chromium.googlesource.com/external/webrtc/+/00a810b844b2393b64f7e36ce...

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

to

==========
Revert of Refactor webrtc/modules/video_processing for GN check (patchset #3
id:40001 of https://codereview.webrtc.org/2595543002/ )

Reason for revert:
This CL broke some buildbots. I will investigate it later.

Original issue's description:
> Refactor webrtc/modules/video_processing for GN check
> 
> This moves some GN check configurations out of .gn to individual
> targets.
> 
> The now checked target is:
> "//webrtc/modules/video_processing/*"
> 
> BUG=webrtc:6828
> NOTRY=True
> 
> Review-Url: https://codereview.webrtc.org/2595543002
> Cr-Commit-Position: refs/heads/master@{#15732}
> Committed:
https://chromium.googlesource.com/external/webrtc/+/00a810b844b2393b64f7e36ce...

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

Review-Url: https://codereview.webrtc.org/2594973002
Cr-Commit-Position: refs/heads/master@{#15733}
Committed:
https://chromium.googlesource.com/external/webrtc/+/d39e16ac300d7947d22b95389...
==========

[commit-bot: I haz the power, 2016-12-21 10:18:58]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/external/webrtc/+/d39e16ac300d7947d22b95389...

[kjellander_webrtc, 2016-12-21 12:47:36]

lgtm

I'm curious what it broke. It's always a good idea to provide a link and/or
error log message in the Revert CL, otherwise it'll be hard to track down the
failure when fixing the problem (which might not happen until weeks later).