Bump Trino version to fix non-working DML queries

[alexandermalyga]

closes: #26774

Issue fixed on Trino's side: trinodb/trino-python-client#220

[eladkal]

Issue reports the issue also on PrestoHook.
Is there a fix for it?

[alexandermalyga]

Issue reports the issue also on PrestoHook. Is there a fix for it?

No, I've tested it with a local Trino deployment and the latest Presto Python client still has the old problematic behaviour.

[eladkal]

Issue reports the issue also on PrestoHook. Is there a fix for it?

No, I've tested it with a local Trino deployment and the latest Presto Python client still has the old problematic behaviour.

Is there an open github issue we can track?

[alexandermalyga]

Issue reports the issue also on PrestoHook. Is there a fix for it?

No, I've tested it with a local Trino deployment and the latest Presto Python client still has the old problematic behaviour.

Is there an open github issue we can track?

Found this open issue since 2019: prestodb/presto-python-client#84
I could try to bring attention to it, but from the comments it doesn't look that they're considering implementing a fix.

[uranusjr]

Please run pre-commit locally to fix the static checks.

[alexandermalyga]

Should the Trino provider version be bumped to 4.1.1 in this PR?

[eladkal]

Should the Trino provider version be bumped to 4.1.1 in this PR?

no. This action is done by release manager as only during release we know if it's patch/minor/major release