Decrease token fetcher timeout to 1 second.

Currently, about 1% of requests takes more than 1 second on desktop.
About 2% of requests takes more than 1 second on Android. For better
user experience, we should move to the next step without waiting
for the token in this case.

Source:
Desktop: http://screen/KiwRQhLVhjp
Android: http://screen/aS2zHNmsMYs

Bug: 1070324
Change-Id: I7e95e14d837ef8210c3b78c87e571359456e6d6b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2246943
Commit-Queue: Xinghui Lu <xinghuilu@chromium.org>
Reviewed-by: Daniel Rubery <drubery@chromium.org>
Cr-Commit-Position: refs/heads/master@{#778589}

components/safe_browsing/core/browser/safe_browsing_token_fetcher.cc

@@ -24,7 +24,7 @@ namespace {
 
 const char kAPIScope[] = "https://www.googleapis.com/auth/chrome-safe-browsing";
 
-const int kTimeoutDelaySeconds = 5 * 60;
+const int kTimeoutDelaySeconds = 1;
 
 }  // namespace