Default timeout is 60s + user define custom timeout per emulator

[erikologic]

Description

Fix #2379
Firestore is failing to start in the hardcoded timeout of 30 secs.
This PR:

• increase the default timeout to 60 secs
• leave open to the user the configuration of the timeout for each emulator in the same pattern of host and port

Scenarios Tested

GIVEN a user does not provide a timeout
WHEN firebase emulators:start is called
THEN firestore emulator will fail to run with Error: TIMEOUT: Port 8081 on localhost was not active within 60000ms

GIVEN a user provides a timeout in firebase.json for firestore of 10ms
WHEN firebase emulators:start --only firestore is called
THEN firestore emulator will fail to run with Error: TIMEOUT: Port 8081 on localhost was not active within 10ms

GIVEN a user provides a timeout in firebase.json for hosting of 10ms
WHEN firebase emulators:start --only firestore is called
THEN firestore emulator will fail to run with Error: TIMEOUT: Port 8081 on localhost was not active within 60000ms*

*I understand these is a bit flacky - couldn't think any better at midnight 😛
I actually tested them with the old value of 30 secs

Sample Commands

In firebase.json:

{
  //...
  "emulators": {
    "auth": {
      "port": 9099
    },
    "firestore": {
      "timeout": 60000,
      "port": 8081
    },
    "hosting": {
      "port": 5000
    },
    "ui": {
      "enabled": true
    }
  }
}

[erikologic]

linting no-sense...

[samtstern]

@mrenrich84 thanks for this! I am in favor of increasing the timeout to 60s but not yet convinced that adding a timeout parameter to the json is the right move. Plus even if it is, we have an internal review process for all API / configuration changes and we'd have to go through that.

Would you mind reducing this PR to just the 30s --> 60s change and then we can have a separate discussion about the timeout configuration?

[erikologic]

😆 😆 😆
Was thinking about that all the time...
What about an env variable to control that timeout value?

[samtstern]

@mrenrich84 I think an env var brings up the same discussion. I'd like to think about a few things before moving forward with more configuration:

• Is there a way we can change the behavior of Firestore imports so that they don't cause timeouts at all?
• If we need timeout configuration, do we need per-emulator timeout configs or should it be global?

[erikologic]

There are few conflicts with the main branch and I'm too lazy to get lost in merge/rebase now 😛
Opened a new PR for just hardcoding the timeout to 60 secs.