In the Postgres connector, the command to create a replication slot halts if there is a long-running query/transaction on the database. The replication slot is only created once the query completes.

When transactions span several minutes, the connector remains stuck in the slot creation command, leading to a poor user experience as users wait for the connector to start without knowing about this limitation.

This change introduces a timeout for the replication slot creation command. The default timeout can be set to 90 seconds. If the command exceeds the timeout, the task should throw a RetriableException, so that the operation can be retried and the user would know about the reason for the delay in task creation.