Revert of Enforce MaxFrameDelayCount in VTVideoEncodeAccelerator and cleanups

Revert of Enforce MaxFrameDelayCount in VTVideoEncodeAccelerator and cleanups (patchset #1 id:1 of https://codereview.chromium.org/2791733002/ )

Reason for revert:
Speculative revert.
Possibly breaks WebRTC Mac FYI bots.
Will reland if the revert does not fix the bots.

Original issue's description:
> Enforce MaxFrameDelayCount in VTVideoEncodeAccelerator and cleanups
> 
> This CL makes sure that we create a HW encoder session only when 
> MaxFrameDelayCount can be set. In case of multiple video streams, Video
> Toolbox can set this variable up to 8, which results in a ~240 ms delay. We 
> should just fall back to SW in those cases.
> Additional cleanups:
> - Remove the unused buffer pool attributes.
> - Since MaxFrameDelayCount can only be set when 
> RequireHardwareAcceleratedVideoEncoder works, remove the other fallback
> logic.
> 
> BUG=707309
> TEST=Demo trying resolutions scaling down https://jsfiddle.net/emircan/jhonduk5/.
> CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
> 
> Review-Url: https://codereview.chromium.org/2791733002
> Cr-Commit-Position: refs/heads/master@{#461245}
> Committed: https://chromium.googlesource.com/chromium/src/+/7cfd3f9eb9dd016c64853f1ae8af84980f9d6f64

TBR=sandersd@chromium.org,emircan@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=707309
Review-Url: https://codereview.chromium.org/2802673002
Cr-Commit-Position: refs/heads/master@{#462053}
Committed: https://chromium.googlesource.com/chromium/src/+/7e6cf6cadac69de4d9c38b71dee1947792ab15d6

[Guido Urdaneta, 2017-04-05 12:39:49]

The CQ bit was checked by guidou@chromium.org

[Guido Urdaneta, 2017-04-05 12:39:50]

Created Revert of Enforce MaxFrameDelayCount in VTVideoEncodeAccelerator and
cleanups

[commit-bot: I haz the power, 2017-04-05 12:40:00]

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

[commit-bot: I haz the power, 2017-04-05 13:39:44]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1491395989722110, "parent_rev":
"8796dadcc5749f8d76d42b123f4b76c007c3c66f", "commit_rev":
"7e6cf6cadac69de4d9c38b71dee1947792ab15d6"}

[commit-bot: I haz the power, 2017-04-05 13:40:34]

Description was changed from

==========
Revert of Enforce MaxFrameDelayCount in VTVideoEncodeAccelerator and cleanups
(patchset #1 id:1 of https://codereview.chromium.org/2791733002/ )

Reason for revert:
Speculative revert.
Possibly breaks WebRTC Mac FYI bots.
Will reland if the revert does not fix the bots.

Original issue's description:
> Enforce MaxFrameDelayCount in VTVideoEncodeAccelerator and cleanups
> 
> This CL makes sure that we create a HW encoder session only when 
> MaxFrameDelayCount can be set. In case of multiple video streams, Video
> Toolbox can set this variable up to 8, which results in a ~240 ms delay. We 
> should just fall back to SW in those cases.
> Additional cleanups:
> - Remove the unused buffer pool attributes.
> - Since MaxFrameDelayCount can only be set when 
> RequireHardwareAcceleratedVideoEncoder works, remove the other fallback
> logic.
> 
> BUG=707309
> TEST=Demo trying resolutions scaling down
https://jsfiddle.net/emircan/jhonduk5/.
>
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
> 
> Review-Url: https://codereview.chromium.org/2791733002
> Cr-Commit-Position: refs/heads/master@{#461245}
> Committed:
https://chromium.googlesource.com/chromium/src/+/7cfd3f9eb9dd016c64853f1ae8af...

TBR=sandersd@chromium.org,emircan@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=707309
==========

to

==========
Revert of Enforce MaxFrameDelayCount in VTVideoEncodeAccelerator and cleanups
(patchset #1 id:1 of https://codereview.chromium.org/2791733002/ )

Reason for revert:
Speculative revert.
Possibly breaks WebRTC Mac FYI bots.
Will reland if the revert does not fix the bots.

Original issue's description:
> Enforce MaxFrameDelayCount in VTVideoEncodeAccelerator and cleanups
> 
> This CL makes sure that we create a HW encoder session only when 
> MaxFrameDelayCount can be set. In case of multiple video streams, Video
> Toolbox can set this variable up to 8, which results in a ~240 ms delay. We 
> should just fall back to SW in those cases.
> Additional cleanups:
> - Remove the unused buffer pool attributes.
> - Since MaxFrameDelayCount can only be set when 
> RequireHardwareAcceleratedVideoEncoder works, remove the other fallback
> logic.
> 
> BUG=707309
> TEST=Demo trying resolutions scaling down
https://jsfiddle.net/emircan/jhonduk5/.
>
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
> 
> Review-Url: https://codereview.chromium.org/2791733002
> Cr-Commit-Position: refs/heads/master@{#461245}
> Committed:
https://chromium.googlesource.com/chromium/src/+/7cfd3f9eb9dd016c64853f1ae8af...

TBR=sandersd@chromium.org,emircan@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=707309

Review-Url: https://codereview.chromium.org/2802673002
Cr-Commit-Position: refs/heads/master@{#462053}
Committed:
https://chromium.googlesource.com/chromium/src/+/7e6cf6cadac69de4d9c38b71dee1...
==========

[commit-bot: I haz the power, 2017-04-05 13:40:35]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/7e6cf6cadac69de4d9c38b71dee1...

[emircan, 2017-04-06 16:06:32]

A revert of this CL (patchset #1 id:1) has been created in
https://codereview.chromium.org/2803673004/ by emircan@chromium.org.

The reason for reverting is: Reland after the MediaRecorder problem is addressed
on https://bugs.chromium.org/p/chromium/issues/detail?id=676424#c3..