Need Trino 431 or later

[MichaelTiemannOSC]

It turns out that Java regexps don't support all the features available in Python regexps (no conditional statement execution), but there is a work-around to write little functions that do the conditional execution manually...if only such little functions can be written. As of 431, I believe they can be: https://trinodb.slack.com/archives/C0305TQ05KL/p1701760286720039?thread_ts=1701702080.522839&cid=C0305TQ05KL

Trino 434 is the latest version of Trino, and presumably that or 435 (expected next week) would be good versions to evaluate as an update to our current 424 version.

[MichaelTiemannOSC]

A caution that we want to see this (near simultaneous inserts into iceberg don't fully commit) resolved before deploying a new version: https://trinodb.slack.com/archives/CJ6UC075E/p1702376393926019. If I were Trino, I'd make this a blocker for 435 and release that when solved. The problem is somewhere between 428 (we are at 424) and 434. No idea whether it's coincidentally 431 (features we need), before that, or after that.

[MichaelTiemannOSC]

My read of the latest on slack is that the Trino folks think that whatever's gone wrong in Iceberg is an Iceberg problem (33 messages back-and-forth and counting). They released 435 in light of this, so I think we should put 435 into the queue as the version to move forward with. They also re-affirmed an aspiration to return to weekly release cadences, so if this goes wrong, we should expect a fix just before Christmas.

[MichaelTiemannOSC]

And now iceberg has a PR addressing the problem: apache/iceberg#9230

[MichaelTiemannOSC]

Another FYI from Trino Slack: https://trinodb.slack.com/archives/CGB0QHWSW/p1702977030476319. Note that Trino team have been testing Java 21 for while, but something is up in the Graviton world. I don't know whether we run Graviton instances or not.