Decouple caching columns from caching table comments in glue for Iceberg

[homar]

Description

Currently, when iceberg.glue.cache-table-metadata is set to true, columns and table comment are either stored together in Glue or none of them is stored.

The goal of this change is to prevent TrinoGlueCatalog from not caching table columns in glue when table comment is too long. It seems wrong that a decision to cache columns depends on the length of the table comment.

This commit changes that and makes storing them in Glue independent from each other.

Additional context and related issues

Release notes

( ) This is not user-visible or is docs only, and no release notes are required.
( ) Release notes are required. Please propose a release note for me.
(x) Release notes are required, with the following suggested text:
Decouple storing columns definition from storing table comments in glue

# Section
* Fix some things. ({issue}`issuenumber`)

[ebyhr]

/test-with-secrets sha=8ec11dff4c3f73b736a6428937659c8fea7e8cfb

[github-actions]

The CI workflow run with tests that require additional secrets has been started: https://github.com/trinodb/trino/actions/runs/11004474695

[ebyhr]

Looks good except for property naming.

[mosabua]

What is the user impact of this change that we can add to the release notes. Currently the suggested entry is just talking about implementation details.

Something like

Ensure table comments are available from Glue even when columns are cached and comment text is long.

but less vague maybe?

Wdyt @martint @ebyhr @homar ?

[homar]

What is the user impact of this change that we can add to the release notes. Currently the suggested entry is just talking about implementation details.

Something like

Ensure table comments are available from Glue even when columns are cached and comment text is long.

but less vague maybe?

Wdyt @martint @ebyhr @homar ?

Something like:
Ensure table columns are cached in glue even when table comment is too long