aw: Move thread hop code to ProviderFactory

aw: Move thread hop code to ProviderFactory

So that the thread hopping code can be used from entry points other
than WebViewChromium.

Large CL, but mostly no-op. Moved these to ProivderFactory:
WebViewChromiumRunQueue
runBlockingFuture
runVoidTaskOnUiThreadBlocking
runOnUiThreadBlocking
addTask

Now FactoryProvider no longer needs to keep a list of WebViewChromiums
yet to be started. So remove all that logic along with startYourEngine,
and no longer need to drainQueue.

Subtle change in behavior is tasks for a single WebViewChromium used to
be grouped together and now are all appended to a single queue that's
drained at start up. This should not cause problems.

BUG=630709
Committed: https://crrev.com/fbfe162dd52f7901535ceb70edf719ef4a692046
Cr-Commit-Position: refs/heads/master@{#407848}

[boliu, 2016-07-25 20:45:18]

boliu@chromium.org changed reviewers:
+ torne@chromium.org

[boliu, 2016-07-25 20:45:19]

part 1

[Torne, 2016-07-26 17:09:49]

LGTM - I like this much better than the old code :)

[boliu, 2016-07-26 17:14:19]

The CQ bit was checked by boliu@chromium.org

[commit-bot: I haz the power, 2016-07-26 17:14:31]

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, 2016-07-26 17:56:53]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-07-26 17:59:27]

Description was changed from

==========
aw: Move thread hop code to ProviderFactory

So that the thread hopping code can be used from entry points other
than WebViewChromium.

Large CL, but mostly no-op. Moved these to ProivderFactory:
WebViewChromiumRunQueue
runBlockingFuture
runVoidTaskOnUiThreadBlocking
runOnUiThreadBlocking
addTask

Now FactoryProvider no longer needs to keep a list of WebViewChromiums
yet to be started. So remove all that logic along with startYourEngine,
and no longer need to drainQueue.

Subtle change in behavior is tasks for a single WebViewChromium used to
be grouped together and now are all appended to a single queue that's
drained at start up. This should not cause problems.

BUG=630709
==========

to

==========
aw: Move thread hop code to ProviderFactory

So that the thread hopping code can be used from entry points other
than WebViewChromium.

Large CL, but mostly no-op. Moved these to ProivderFactory:
WebViewChromiumRunQueue
runBlockingFuture
runVoidTaskOnUiThreadBlocking
runOnUiThreadBlocking
addTask

Now FactoryProvider no longer needs to keep a list of WebViewChromiums
yet to be started. So remove all that logic along with startYourEngine,
and no longer need to drainQueue.

Subtle change in behavior is tasks for a single WebViewChromium used to
be grouped together and now are all appended to a single queue that's
drained at start up. This should not cause problems.

BUG=630709

Committed: https://crrev.com/fbfe162dd52f7901535ceb70edf719ef4a692046
Cr-Commit-Position: refs/heads/master@{#407848}
==========

[commit-bot: I haz the power, 2016-07-26 17:59:28]

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