Add auth type to SecondDeviceAuthBroker usage of EndpointFetcher

crrev.com/c/6901994 migrated SecondDeviceAuthBroker
to use the new EndpoitnFetcher. It was missed that
the previous constructor used Chrome API key
authentication under the hood. We now require clients
to explicitly state the authentication they are
using.

Bug: 439911463
Change-Id: I797c381d04491d5b8b881edf8b9274a625f554a7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6940585
Commit-Queue: David Maunder <davidjm@chromium.org>
Reviewed-by: Brittany Hartmire <bhartmire@google.com>
Cr-Commit-Position: refs/heads/main@{#1514515}

chrome/browser/ash/login/oobe_quick_start/second_device_auth_broker.cc

diff --git a/chrome/browser/ash/login/oobe_quick_start/second_device_auth_broker.cc b/chrome/browser/ash/login/oobe_quick_start/second_device_auth_broker.cc
index e9cc495d..28dad83 100644
--- a/chrome/browser/ash/login/oobe_quick_start/second_device_auth_broker.cc
+++ b/chrome/browser/ash/login/oobe_quick_start/second_device_auth_broker.cc
@@ -531,6 +531,7 @@
       /*identity_manager=*/nullptr,
       EndpointFetcher::RequestParams::Builder(kHttpPost,
                                               kChallengeDataAnnotation)
+          .SetAuthType(endpoint_fetcher::CHROME_API_KEY)
           .SetChannel(ash::GetChannel())
           .SetContentType(kHttpContentType)
           .SetPostData(kGetChallengeDataRequest)