Upgrade Trino on cl1 to match version deployed on cl2

[redmikhail]

upgrade both clusters to 397 (@redmikhail to verify)

[HeatherAck]

@redmikhail still working on this - planned for wk of 13-Mar

[HeatherAck]

@redmikhail will reassign to @ryanaslett

[HeatherAck]

to complete week of 27-Mar

[HeatherAck]

@ryanaslett to work on week of 17-apr

[HeatherAck]

@ryanaslett to work on week of 24-apr

[HeatherAck]

4.14 version would be useful relative to iceberg corruption we experienced in the past

[HeatherAck]

@ryanaslett to complete after superset upgrade week of 8-May

[HeatherAck]

@redmikhail to own the upgrade to ensure versions are same - week of 12-June

[HeatherAck]

will be done week of 19-June

[MightyNerdEric]

It took a few days, but Trino on cl1 is now in a working state with v398 (we still have one more commit to merge, but it's currently running with a manual override of the same config). Once that last PR is merged, barring any regressions, this can be closed and we can move on with #171.

[MightyNerdEric]

With the PR merged, Trino on cl1 is at v398 and working as expected. This issue can be closed.

[ModeSevenIndustrialSolutions]

See:
https://github.com/os-climate/ops-argocd