Reland of Add task queue to Call.

This reverts commit 8eb37a39e79fe1098d3503dcb8c8c2d196203fed. Chrome now have its own implementation of TaskQueues that is based on Chrome threads.

cl was originally reviewed here:
https://codereview.webrtc.org/2060403002/

- Add task queue to Call with the intent of replacing the use of one of the process threads.

- Split VideoSendStream in two. VideoSendStreamInternal is created and used on the new task queue.

- BitrateAllocator is now created on libjingle's worker thread but always used on the new task queue instead of both encoder threads and the process thread.

- VideoEncoderConfig and VideoSendStream::Config support move semantics.

- The encoder thread is moved from VideoSendStream to ViEEncoder. Frames are forwarded directly to ViEEncoder which is responsible for timestamping ? and encoding the frames.

TBR=mflodman@webrtc.org
BUG=webrtc:5687, webrtc:6289, webrtc:4212
Committed: https://crrev.com/26091b1118e37b5cbbfe0de9869127fd5c1b01d0
Cr-Commit-Position: refs/heads/master@{#14014}

[perkj_webrtc, 2016-09-01 07:28:36]

Description was changed from

==========
Revert "Revert of Add task queue to Call. (patchset #42 id:840001 of
https://codereview.webrtc.org/2060403002/ )"

This reverts commit 8eb37a39e79fe1098d3503dcb8c8c2d196203fed.

BUG=
==========

to

==========
This reverts commit 8eb37a39e79fe1098d3503dcb8c8c2d196203fed.

- Add task queue to Call with the intent of replacing the use of one of the
process threads.

- Split VideoSendStream in two. VideoSendStreamInternal is created and used on
the new task queue.

- BitrateAllocator is now created on libjingle's worker thread but always used
on the new task queue instead of both encoder threads and the process thread.

- VideoEncoderConfig and VideoSendStream::Config support move semantics.

- The encoder thread is moved from VideoSendStream to ViEEncoder. Frames are
forwarded directly to ViEEncoder which is responsible for timestamping ? and
encoding the frames.

BUG=webrtc:5687
==========

[perkj_webrtc, 2016-09-01 07:38:24]

perkj@webrtc.org changed reviewers:
+ mflodman@webrtc.org

[perkj_webrtc, 2016-09-01 07:40:10]

Description was changed from

==========
This reverts commit 8eb37a39e79fe1098d3503dcb8c8c2d196203fed.

- Add task queue to Call with the intent of replacing the use of one of the
process threads.

- Split VideoSendStream in two. VideoSendStreamInternal is created and used on
the new task queue.

- BitrateAllocator is now created on libjingle's worker thread but always used
on the new task queue instead of both encoder threads and the process thread.

- VideoEncoderConfig and VideoSendStream::Config support move semantics.

- The encoder thread is moved from VideoSendStream to ViEEncoder. Frames are
forwarded directly to ViEEncoder which is responsible for timestamping ? and
encoding the frames.

BUG=webrtc:5687
==========

to

==========
This reverts commit 8eb37a39e79fe1098d3503dcb8c8c2d196203fed.

cl was originally reviewed here:
https://codereview.webrtc.org/2060403002/

- Add task queue to Call with the intent of replacing the use of one of the
process threads.

- Split VideoSendStream in two. VideoSendStreamInternal is created and used on
the new task queue.

- BitrateAllocator is now created on libjingle's worker thread but always used
on the new task queue instead of both encoder threads and the process thread.

- VideoEncoderConfig and VideoSendStream::Config support move semantics.

- The encoder thread is moved from VideoSendStream to ViEEncoder. Frames are
forwarded directly to ViEEncoder which is responsible for timestamping ? and
encoding the frames.

BUG=webrtc:5687
==========

[perkj_webrtc, 2016-09-01 07:40:52]

Description was changed from

==========
This reverts commit 8eb37a39e79fe1098d3503dcb8c8c2d196203fed.

cl was originally reviewed here:
https://codereview.webrtc.org/2060403002/

- Add task queue to Call with the intent of replacing the use of one of the
process threads.

- Split VideoSendStream in two. VideoSendStreamInternal is created and used on
the new task queue.

- BitrateAllocator is now created on libjingle's worker thread but always used
on the new task queue instead of both encoder threads and the process thread.

- VideoEncoderConfig and VideoSendStream::Config support move semantics.

- The encoder thread is moved from VideoSendStream to ViEEncoder. Frames are
forwarded directly to ViEEncoder which is responsible for timestamping ? and
encoding the frames.

BUG=webrtc:5687
==========

to

==========
This reverts commit 8eb37a39e79fe1098d3503dcb8c8c2d196203fed. Chrome now have
its own implementation of TaskQueues that is based on Chrome threads.

cl was originally reviewed here:
https://codereview.webrtc.org/2060403002/

- Add task queue to Call with the intent of replacing the use of one of the
process threads.

- Split VideoSendStream in two. VideoSendStreamInternal is created and used on
the new task queue.

- BitrateAllocator is now created on libjingle's worker thread but always used
on the new task queue instead of both encoder threads and the process thread.

- VideoEncoderConfig and VideoSendStream::Config support move semantics.

- The encoder thread is moved from VideoSendStream to ViEEncoder. Frames are
forwarded directly to ViEEncoder which is responsible for timestamping ? and
encoding the frames.

BUG=webrtc:5687
==========

[perkj_webrtc, 2016-09-01 07:41:13]

Description was changed from

==========
This reverts commit 8eb37a39e79fe1098d3503dcb8c8c2d196203fed. Chrome now have
its own implementation of TaskQueues that is based on Chrome threads.

cl was originally reviewed here:
https://codereview.webrtc.org/2060403002/

- Add task queue to Call with the intent of replacing the use of one of the
process threads.

- Split VideoSendStream in two. VideoSendStreamInternal is created and used on
the new task queue.

- BitrateAllocator is now created on libjingle's worker thread but always used
on the new task queue instead of both encoder threads and the process thread.

- VideoEncoderConfig and VideoSendStream::Config support move semantics.

- The encoder thread is moved from VideoSendStream to ViEEncoder. Frames are
forwarded directly to ViEEncoder which is responsible for timestamping ? and
encoding the frames.

BUG=webrtc:5687
==========

to

==========
This reverts commit 8eb37a39e79fe1098d3503dcb8c8c2d196203fed. Chrome now have
its own implementation of TaskQueues that is based on Chrome threads.

cl was originally reviewed here:
https://codereview.webrtc.org/2060403002/

- Add task queue to Call with the intent of replacing the use of one of the
process threads.

- Split VideoSendStream in two. VideoSendStreamInternal is created and used on
the new task queue.

- BitrateAllocator is now created on libjingle's worker thread but always used
on the new task queue instead of both encoder threads and the process thread.

- VideoEncoderConfig and VideoSendStream::Config support move semantics.

- The encoder thread is moved from VideoSendStream to ViEEncoder. Frames are
forwarded directly to ViEEncoder which is responsible for timestamping ? and
encoding the frames.

TBR=mflodman@webrtc.org
BUG=webrtc:5687
==========

[perkj_webrtc, 2016-09-01 07:41:20]

The CQ bit was checked by perkj@webrtc.org

[commit-bot: I haz the power, 2016-09-01 07:41:31]

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-09-01 08:17:42]

Description was changed from

==========
This reverts commit 8eb37a39e79fe1098d3503dcb8c8c2d196203fed. Chrome now have
its own implementation of TaskQueues that is based on Chrome threads.

cl was originally reviewed here:
https://codereview.webrtc.org/2060403002/

- Add task queue to Call with the intent of replacing the use of one of the
process threads.

- Split VideoSendStream in two. VideoSendStreamInternal is created and used on
the new task queue.

- BitrateAllocator is now created on libjingle's worker thread but always used
on the new task queue instead of both encoder threads and the process thread.

- VideoEncoderConfig and VideoSendStream::Config support move semantics.

- The encoder thread is moved from VideoSendStream to ViEEncoder. Frames are
forwarded directly to ViEEncoder which is responsible for timestamping ? and
encoding the frames.

TBR=mflodman@webrtc.org
BUG=webrtc:5687
==========

to

==========
This reverts commit 8eb37a39e79fe1098d3503dcb8c8c2d196203fed. Chrome now have
its own implementation of TaskQueues that is based on Chrome threads.

cl was originally reviewed here:
https://codereview.webrtc.org/2060403002/

- Add task queue to Call with the intent of replacing the use of one of the
process threads.

- Split VideoSendStream in two. VideoSendStreamInternal is created and used on
the new task queue.

- BitrateAllocator is now created on libjingle's worker thread but always used
on the new task queue instead of both encoder threads and the process thread.

- VideoEncoderConfig and VideoSendStream::Config support move semantics.

- The encoder thread is moved from VideoSendStream to ViEEncoder. Frames are
forwarded directly to ViEEncoder which is responsible for timestamping ? and
encoding the frames.

TBR=mflodman@webrtc.org
BUG=webrtc:5687
==========

[commit-bot: I haz the power, 2016-09-01 08:17:44]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2016-09-01 08:17:51]

Description was changed from

==========
This reverts commit 8eb37a39e79fe1098d3503dcb8c8c2d196203fed. Chrome now have
its own implementation of TaskQueues that is based on Chrome threads.

cl was originally reviewed here:
https://codereview.webrtc.org/2060403002/

- Add task queue to Call with the intent of replacing the use of one of the
process threads.

- Split VideoSendStream in two. VideoSendStreamInternal is created and used on
the new task queue.

- BitrateAllocator is now created on libjingle's worker thread but always used
on the new task queue instead of both encoder threads and the process thread.

- VideoEncoderConfig and VideoSendStream::Config support move semantics.

- The encoder thread is moved from VideoSendStream to ViEEncoder. Frames are
forwarded directly to ViEEncoder which is responsible for timestamping ? and
encoding the frames.

TBR=mflodman@webrtc.org
BUG=webrtc:5687
==========

to

==========
This reverts commit 8eb37a39e79fe1098d3503dcb8c8c2d196203fed. Chrome now have
its own implementation of TaskQueues that is based on Chrome threads.

cl was originally reviewed here:
https://codereview.webrtc.org/2060403002/

- Add task queue to Call with the intent of replacing the use of one of the
process threads.

- Split VideoSendStream in two. VideoSendStreamInternal is created and used on
the new task queue.

- BitrateAllocator is now created on libjingle's worker thread but always used
on the new task queue instead of both encoder threads and the process thread.

- VideoEncoderConfig and VideoSendStream::Config support move semantics.

- The encoder thread is moved from VideoSendStream to ViEEncoder. Frames are
forwarded directly to ViEEncoder which is responsible for timestamping ? and
encoding the frames.

TBR=mflodman@webrtc.org
BUG=webrtc:5687

Committed: https://crrev.com/26091b1118e37b5cbbfe0de9869127fd5c1b01d0
Cr-Commit-Position: refs/heads/master@{#14014}
==========

[commit-bot: I haz the power, 2016-09-01 08:17:52]

Patchset 3 (id:??) landed as
https://crrev.com/26091b1118e37b5cbbfe0de9869127fd5c1b01d0
Cr-Commit-Position: refs/heads/master@{#14014}

[perkj_webrtc, 2016-09-01 09:38:31]

Description was changed from

==========
This reverts commit 8eb37a39e79fe1098d3503dcb8c8c2d196203fed. Chrome now have
its own implementation of TaskQueues that is based on Chrome threads.

cl was originally reviewed here:
https://codereview.webrtc.org/2060403002/

- Add task queue to Call with the intent of replacing the use of one of the
process threads.

- Split VideoSendStream in two. VideoSendStreamInternal is created and used on
the new task queue.

- BitrateAllocator is now created on libjingle's worker thread but always used
on the new task queue instead of both encoder threads and the process thread.

- VideoEncoderConfig and VideoSendStream::Config support move semantics.

- The encoder thread is moved from VideoSendStream to ViEEncoder. Frames are
forwarded directly to ViEEncoder which is responsible for timestamping ? and
encoding the frames.

TBR=mflodman@webrtc.org
BUG=webrtc:5687

Committed: https://crrev.com/26091b1118e37b5cbbfe0de9869127fd5c1b01d0
Cr-Commit-Position: refs/heads/master@{#14014}
==========

to

==========
This reverts commit 8eb37a39e79fe1098d3503dcb8c8c2d196203fed. Chrome now have
its own implementation of TaskQueues that is based on Chrome threads.

cl was originally reviewed here:
https://codereview.webrtc.org/2060403002/

- Add task queue to Call with the intent of replacing the use of one of the
process threads.

- Split VideoSendStream in two. VideoSendStreamInternal is created and used on
the new task queue.

- BitrateAllocator is now created on libjingle's worker thread but always used
on the new task queue instead of both encoder threads and the process thread.

- VideoEncoderConfig and VideoSendStream::Config support move semantics.

- The encoder thread is moved from VideoSendStream to ViEEncoder. Frames are
forwarded directly to ViEEncoder which is responsible for timestamping ? and
encoding the frames.

TBR=mflodman@webrtc.org
BUG=webrtc:5687, webrtc:6289

Committed: https://crrev.com/26091b1118e37b5cbbfe0de9869127fd5c1b01d0
Cr-Commit-Position: refs/heads/master@{#14014}
==========

[mflodman, 2016-09-08 09:24:01]

LGTM

[perkj_webrtc, 2016-09-20 09:05:34]

Description was changed from

==========
This reverts commit 8eb37a39e79fe1098d3503dcb8c8c2d196203fed. Chrome now have
its own implementation of TaskQueues that is based on Chrome threads.

cl was originally reviewed here:
https://codereview.webrtc.org/2060403002/

- Add task queue to Call with the intent of replacing the use of one of the
process threads.

- Split VideoSendStream in two. VideoSendStreamInternal is created and used on
the new task queue.

- BitrateAllocator is now created on libjingle's worker thread but always used
on the new task queue instead of both encoder threads and the process thread.

- VideoEncoderConfig and VideoSendStream::Config support move semantics.

- The encoder thread is moved from VideoSendStream to ViEEncoder. Frames are
forwarded directly to ViEEncoder which is responsible for timestamping ? and
encoding the frames.

TBR=mflodman@webrtc.org
BUG=webrtc:5687, webrtc:6289

Committed: https://crrev.com/26091b1118e37b5cbbfe0de9869127fd5c1b01d0
Cr-Commit-Position: refs/heads/master@{#14014}
==========

to

==========
This reverts commit 8eb37a39e79fe1098d3503dcb8c8c2d196203fed. Chrome now have
its own implementation of TaskQueues that is based on Chrome threads.

cl was originally reviewed here:
https://codereview.webrtc.org/2060403002/

- Add task queue to Call with the intent of replacing the use of one of the
process threads.

- Split VideoSendStream in two. VideoSendStreamInternal is created and used on
the new task queue.

- BitrateAllocator is now created on libjingle's worker thread but always used
on the new task queue instead of both encoder threads and the process thread.

- VideoEncoderConfig and VideoSendStream::Config support move semantics.

- The encoder thread is moved from VideoSendStream to ViEEncoder. Frames are
forwarded directly to ViEEncoder which is responsible for timestamping ? and
encoding the frames.

TBR=mflodman@webrtc.org
BUG=webrtc:5687, webrtc:6289, webrtc:4212

Committed: https://crrev.com/26091b1118e37b5cbbfe0de9869127fd5c1b01d0
Cr-Commit-Position: refs/heads/master@{#14014}
==========