Change the Docker Image used by the Presto module to prestodb/presto

[linghengqian]

• Fixes [Feature]: Presto Module uses the outdated Docker Image of ghcr.io/trinodb/presto and needs to be updated to prestodb/presto #8657 .
• Change the Docker Image used by the Presto module to prestodb/presto.

[eddumelendez]

Thanks for your contribution, @linghengqian! In order to fix the build, please run ./gradlew :presto:spotlessApply.

[linghengqian]

Thanks for your contribution, @linghengqian! In order to fix the build, please run ./gradlew :presto:spotlessApply.

• To keep the original unit tests, I added a few Presto Connector files. There are some additional differences.
• Presto does not support calling setAutoCommit repeatedly on the same Connection. See SQLException thrown when Connection.setAutoCommit(false) and then Connection.setAutoCommit(false); prestodb/presto#15916 .
• Presto does not support the ON TRUE condition for CROSS JOIN UNNEST syntax, and Presto does not support the LEFT JOIN UNNEST syntax. See Broaden the join types that can be used with UNNEST. prestodb/presto#8200 .
• Presto does not support the FETCH FIRST N ROWS WITH TIES syntax. See Lack of support for the ANSI SQL syntax FETCH FIRST N ROWS WITH TIES prestodb/presto#23223 .
• I will say that I’m not really sure why unit tests often result in Caused by: com.facebook.presto.spi.PrestoException: No nodes available to run query, as I haven’t been able to find a simple healthCheck method in the Presto documentation that can replace the following. Refer to Missing an HTTP endpoint to ensure the Presto Docker Container is ready prestodb/presto#23226 .

this.waitStrategy =
            new LogMessageWaitStrategy()
                .withRegEx(".*======== SERVER STARTED ========.*")
                .withStartupTimeout(Duration.of(60, ChronoUnit.SECONDS));

[eddumelendez]

thanks for the update, @linghengqian ! I see everything green but failing locally. So, hopefully the other issue in presto repository is solved soon and the module can provide a reliable wait strategy.

[linghengqian]

• Since prestodb/presto#23226 and prestodb/presto#15916 have been resolved, it seems that there is nothing that can prevent the current PR from continuing to merge.

[linghengqian]

After updating from presto 0.292 to presto 0.296, CI suddenly returned to normal.

I'm not sure if the bug mentioned in #3079 (comment) has been fixed.

The cause of this appears to be that JdbcDatabaseContainer ignores any configured wait strategies.