1. Proposed title of this feature request
Unclear OpenShift installer `Service Account (absolute path to file) [Enter 2 empty lines to finish]` prompt leads to "context deadline exceeded"

2. What is the nature and description of the request?
When installing RHOCP cluster in Google Cloud, the installer provides `Service Account (absolute path to file) [Enter 2 empty lines to finish]` prompt if`~/.gcp/osServiceAccount.json` file does not exists.
The prompt wording` [Enter 2 empty lines to finish]` is a bit unclear. As in should we hit Enter key twice or thrice?

I notice a pattern that while using an absolute Service Account file path and hitting Enter key twice then the installer is still waiting for the 3rd Enter key. And any more than 55secs delay in hitting the Enter key for the 3rd time comes with `.... context deadline exceeded` and halts cluster installation.
Note: This delay time also varies. Sometimes, it timesouts even with 30secs delay and other times any delay >55secs leads to `.... context deadline exceeded` and the installer stops.

$ ll cee-gcp-apac-vbh-sa.json 
{-}rw-r{-}{-}r{-}-. 1 vibhutichalise vibhutichalise 2384 Feb 25 11:21 cee-gcp-apac-vbh-sa.json

$ openshift-install create cluster --dir create-cluster/ --log-level=info
? SSH Public Key /home/vibhutichalise/.ssh/rammy.pub
? Platform gcp
? Service Account (absolute path to file) [Enter 2 empty lines to finish]/home/vibhutichalise/Downloads/cee-gcp-apac-vbh-sa.json

? Service Account (absolute path to file) 
/home/vibhutichalise/Downloads/cee-gcp-apac-vbh-sa.json
INFO Saving the credentials to "/home/vibhutichalise/.gcp/osServiceAccount.json" 
INFO Credentials loaded from file "/home/vibhutichalise/.gcp/osServiceAccount.json" 
FATAL failed to fetch Metadata: failed to fetch dependency of "Metadata": failed to fetch dependency of "Cluster ID": failed to fetch dependency of "Install Config": failed to fetch dependency of "Base Domain": failed to generate asset "Platform": failed to get projects: context deadline exceeded

3. Why does the customer need this? (List the business requirements here)
The prompt is unclear. Can the wording of the prompt can be changed to something like `Service Account (absolute path to file) [Hit Enter key thrice]` ?
Or else, the timeout threshold be fixed and made clear in the prompt?

4. List any affected packages or components.
Althouth the behaviour may be present in older versions too which I haven't test yet, this was specifically tested in `openshift-install v4.21.1`:

$ openshift-install version
openshift-install 4.21.1
built from commit 2c105c33e9e373b6e66c9ef8814f78a72539ae53
release image quay.io/openshift-release-dev/ocp-release@sha256:7ca8870aa5e505f969aa26161594a3f99b65baf7d29bab8adaca0cade51b0bb6
release architecture amd64