Speculative fix for TaskQueueImpl::PostImmediateTaskImpl priority inversion

It turns out base::MessagePumpForUI::ScheduleWork() can be surprisingly expensive on
the IO thread on windows. See:
https://uma.googleplex.com/p/chrome/callstacks?sid=ad8c32eaded1021fafa922b9cc2f320f

We suspect this is a priority inversion, For more details see:
https://groups.google.com/a/chromium.org/forum/#!msg/scheduler-dev/jYA3SYZ1aDc/7lz1P-GvDQAJ

Bug: 930834
Change-Id: I7a95d0da1f650556589a82704fa3868777ca573b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1503325
Commit-Queue: Alex Clarke <alexclarke@chromium.org>
Reviewed-by: Sami Kyöstilä <skyostil@chromium.org>
Reviewed-by: Alexander Timin <altimin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#637680}
1 file changed