Separate API key from client ID and secret.

The CL separates the HasAPIKeysConfigured in HasAPIKeyConfigured and
HasOAuthClientConfigured. It then disables Desktop Identity Consistency
when the OAuth client ID and secret are not configured.

That allows developers to set and API key without having to also configure
the OAuth client ID and client secret. In such an environment, Chromium
would continue to use the non-authorized Google APIs (e.g geolocation,
translate, safe browsing etc), while at the same time being able to
sign in to Google web properties.

Bug: 854166

Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: I9606c5d34e57823e47466bf4fc02f258ecd262a8
Reviewed-on: https://chromium-review.googlesource.com/1105991
Commit-Queue: Mihai Sardarescu <[email protected]>
Reviewed-by: Scott Violet <[email protected]>
Reviewed-by: David Roger <[email protected]>
Reviewed-by: Roger Tawa <[email protected]>
Cr-Commit-Position: refs/heads/master@{#568882}
12 files changed