arc: Increase android container startup timeout

Workaround for patchoat intermittently taking much longer than normal to
complete on startup. This will be reverted once issue is root caused and
fixed.

Bug: 117832337
Test: Add a sleep 30 before patchoat and ensure container starts
Change-Id: I3c66110dff876b8aa61fa4fb12c658038db978a3
Reviewed-on: https://chromium-review.googlesource.com/c/1322352
Commit-Queue: Christopher Morin <cmtm@google.com>
Reviewed-by: Ryo Hashimoto <hashimoto@chromium.org>
Reviewed-by: Yusuke Sato <yusukes@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606205}

chromeos/dbus/session_manager_client.cc

@@ -43,6 +43,8 @@ using RetrievePolicyResponseType =
     SessionManagerClient::RetrievePolicyResponseType;
 
 constexpr char kEmptyAccountId[] = "";
+// The timeout used when starting the android container is 90 seconds
+constexpr int kStartArcTimeout = 90 * 1000;
 
 // Helper to get the enum type of RetrievePolicyResponseType based on error
 // name.
@@ -403,7 +405,7 @@ class SessionManagerClientImpl : public SessionManagerClient {
     writer.AppendProtoAsArrayOfBytes(request);
 
     session_manager_proxy_->CallMethod(
-        &method_call, dbus::ObjectProxy::TIMEOUT_USE_DEFAULT,
+        &method_call, kStartArcTimeout,
         base::BindOnce(&SessionManagerClientImpl::OnStartArcMiniContainer,
                        weak_ptr_factory_.GetWeakPtr(), std::move(callback)));
   }