Increase default server start timeout in Open Liberty stack

[makandre]

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

In our regular use and test with the Open Liberty stack (via Codewind), we intermittently run into the server not starting within the default 120 second timeout:

[Container] [INFO] CWWKM2010I: Searching for CWWKF0011I: in /opt/ol/wlp/usr/servers/defaultServer/logs/messages.log. This search will timeout after 120 seconds.
[Container] [INFO] CWWKM2013I: The file /opt/ol/wlp/usr/servers/defaultServer/logs/messages.log being validated does not exist.
...
[Container] [INFO] CWWKM2011E: Timed out searching for CWWKF0011I: in /opt/ol/wlp/usr/servers/defaultServer/logs/messages.log.
...
[Container] [ERROR] Failed to execute goal io.openliberty.tools:liberty-maven-plugin:3.2:dev (default-cli) on project starter-app: Unable to verify if the server was started after 120 seconds.  Consider increasing the serverStartTimeout value if this continues to occur. -> [Help 1]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Although users can quite easily increase the server start timeout themselves in the pom.xml, I was wondering if we could increase the server start timeout value in the template to reduce the likelihood of users running into this in the first place?

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

[scottkurz]

Might be worth considering, sure... there is some perf. overhead running in the container on a given system compared to outside the container. Still, raising this much more than 2 minutes is a long time to leave the user who has legitimately messed something up waiting for a failure. Let's think about it.