Allow timeout configuration based on parameter or environment

[jose-ricardo-health]

Waiting 120 seconds on the dev environment (or constantly editing the behat.yml) is overwhelming, so I suggest an improvement that allows tests to retry faster when needed.

Some possibilities are:

• A new configuration for dev environment (based on .env file), something like dev-timeout
• A parameter to the behat command, something like --retry-timeout, that could be used on staging to set 120, while the behat.yml could have a lower amount

[Chekote]

Thanks for the suggestion. I agree that 120 is excessive, but it was originally explicitly set to this high value to address issues with infrastructure timing. As we've continued to make improvements in that area, the intent is to gradually ratchet down that value until we can find a sweet spot of failing early vs being resilient to the remaining infrastructure performance fluctiations.

In the meantime, we can certainly pursue your proposal to offer some flexibility.