[TaskScheduler] Do not limit concurrent background sequences during shutdown.

Background sequences are often used to write data to disk. During
normal execution, it is not urgent to run these tasks, but during
shutdown, they should run as quickly as possible to allow the
process to exit.

Another reason not to limit concurrent background sequences
during shutdown is to support a --disable-background-tasks flag.
With this flag, Chrome doesn't run any background tasks during
normal execution. It does however need to run these tasks on
shutdown for correctness.

Bug: 726937
Change-Id: I4ca1b34ad293620acd8a148479c94a59ef2a2c85
Reviewed-on: https://chromium-review.googlesource.com/914447
Reviewed-by: Gabriel Charette <gab@chromium.org>
Reviewed-by: Robert Liao <robliao@chromium.org>
Commit-Queue: François Doray <fdoray@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536419}

CrOS-Libchrome-Original-Commit: 762ffa9585784d093784efe1b6a27a04ede24fd9
3 files changed
tree: ffde1b1d31f8b1db6f48faa2b555f12279f5c78f
  1. base/
  2. build/
  3. components/
  4. dbus/
  5. device/
  6. ipc/
  7. mojo/
  8. testing/
  9. third_party/
  10. ui/