Postgres Container with default configuration doesnt work with mapped data binding

The default configuration for PostgreSQLContainer doesn't work if a non-empty data bind is configured.

For example:

final JdbcDatabaseContainer<?> container = new PostgreSQLContainerProvider().newInstance("13.4");
container.addFileSystemBind("./target/postgres-volume", "/var/lib/postgresql/data", BindMode.READ_WRITE);
container.start();

blocks for 60 seconds until it finally throws an exception because the default WaitStrategy didnt finish within 60 seconds.

This happens because the Log-Output of a Postgres-Container with an existing data-directory doesn't contain the configured log-message twice, but only once.
When configuring the same WaitStrategy expecting the output to be present only once, the startup works as expected:

        container.setWaitStrategy(new LogMessageWaitStrategy()
                .withRegEx(".*database system is ready to accept connections.*\\s")
                .withTimes(1)
                .withStartupTimeout(Duration.of(60, SECONDS)));

Proposed Solution:
The default WaitStrategy should first wait for either:
PostgreSQL Database directory appears to contain a database; Skipping initialization
-- or --
.*database system is ready to accept connections.*\s

and after that, wait for:
.*database system is ready to accept connections.*\s

Start at PostgreSQLContainer and its default LogMessageWaitStrategy, then reproduce the issue with PostgreSQLContainerProvider, addFileSystemBind, and a non-empty data directory. Verify startup for both initialized and existing data directories, including the expected log-message sequence and timeout behavior.