OrientDB: Use log wait strategy for more reliable readiness detection

[rnorth]

TODO: check whether this log message is universally applicable or whether we need to include an alternative string to match for

[rnorth]

Interesting; I thought we'd be able to look for .*(OrientDB Server is active|Gremlin started correctly).* but it appears that the first of these two strings only appears in the logs when using an interactive run of the cotainer (i.e. docker run -i ...).

As far as I can tell Gremlin started correctly is the string we should be looking for.

[kiview]

Further, these logs strongly indicate that network connectivity is provided before general application readiness:

2021-09-20 12:34:53:131 INFO  Listening binary connections on 0.0.0.0:2424 (protocol v.37, socket=default) [OServerNetworkListener]
2021-09-20 12:34:53:134 INFO  Listening http connections on 0.0.0.0:2480 (protocol v.10, socket=default) [OServerNetworkListener]
2021-09-20 12:34:53:136 INFO  Found ORIENTDB_ROOT_PASSWORD variable, using this value as root's password [OServer]
2021-09-20 12:34:53:455 INFO  Installing dynamic plugin 'orientdb-etl-3.0.24.jar'... [OServerPluginManager]
2021-09-20 12:34:53:459 INFO  Installing dynamic plugin 'orientdb-studio-3.0.24.zip'... [OServerPluginManager]

In this case, the Gremlin log you suggested to use is logged 2 seconds later. So this should provide much better reliability.