Android: moving download onclick execution to thread pool

Currently, AsyncTask.execute() defaults to the SERIAL_EXECUTOR. This
exector is good for preventing concurrency errors since it guarantees
serial execution, but bad for performance since the entire app shares
this single queue.

It looks like this callsite can use the THREAD_POOL_EXECUTOR instead,
since this use doesn't appear to rely on the concurrency guarantees that
SERIAL_EXECUTOR provides.

Bug: 869907
Change-Id: Iad83ebccb137eec01ff32bc1f78d72047859efc8
Reviewed-on: https://chromium-review.googlesource.com/1158789Reviewed-by: Matthew Jones <mdjones@chromium.org>
Commit-Queue: Sam Maier <smaier@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579915}

chrome/android/java/src/org/chromium/chrome/browser/infobar/DuplicateDownloadInfoBar.java

@@ -95,7 +95,8 @@ public class DuplicateDownloadInfoBar extends ConfirmInfoBar {
                                     ContextUtils.getApplicationContext());
                         }
                     }
-                }.execute();
+                }
+                        .executeOnExecutor(AsyncTask.THREAD_POOL_EXECUTOR);
             }
         });
     }