Make database version check more reliable on API install

[johnstairs]

tyger api install checks for a log message from the database init container indicating whether the database version could be upgraded of whether it is the most recent. This check fails sometimes because the database init process lifetime can be short and it would seem the the log lines are not always picked up.

Two parts to the fix:

1. Adding the message as well to the main tyger server process (both container's logs are inspected)
2. Raising a warning instead of failing the installation if the log message cannot be found. There is still an error if the database version it too old for the code.