We need a cleaner startup solution.  There is some investigation that needs to happen before we can finish this task.

Investigation:
(1) Figure out what the impact of querying for the DownloadManager is.  Do we spin up a DownloadManager early in Chrome's startup or do we always spin it up on demand?

Changes:
(2) Some suggested rule changes:
  - Have the service start downloading X seconds after Chrome launches an Activity.
  - Have the service start immediately if we're triggered by our job.
  - Have the service start immediately if a component tries to start a download or interact with the service.