Fix printing --starter.instance-up-timeout instead of hardcoded value (#361)

Author: nikita-vanyasin

CHANGELOG.md

@@ -1,6 +1,7 @@
 # ArangoDB Starter Changelog
 
 ## [master](https://github.com/arangodb-helper/arangodb/tree/master) (N/A)
+- Fix printing --starter.instance-up-timeout instead of hardcoded value
 - Fix context handling in WaitUntilStarterReady for tests
 
 ## [0.15.8](https://github.com/arangodb-helper/arangodb/tree/0.15.8) (2023-06-02)

service/process_wrapper.go

@@ -221,7 +221,7 @@ func (p *processWrapper) run(startedCh chan<- struct{}) {
 							}
 						}
 					} else if !up {
-						logProcess.Warn().Msgf("%s not ready after 5min!: Status trail: %#v", p.serverType, statusTrail)
+						logProcess.Warn().Msgf("%s not ready after %s! Status trail: %#v", p.config.InstanceUpTimeout, p.serverType, statusTrail)
 					} else if !correctRole {
 						expectedRole, expectedMode := p.serverType.ExpectedServerRole()
 						logProcess.Warn().Msgf("%s does not have the expected role of '%s,%s' (but '%s,%s'): Status trail: %#v", p.serverType, expectedRole, expectedMode, role, mode, statusTrail)