What this PR does / why we need it:

Problem

TrinoOfflineStore.query_monitoring_metrics catches every TrinoQueryError, logs it at debug level and returns []. The test for it, test_query_monitoring_metrics_handles_query_error, uses TABLE_NOT_FOUND, and that case is right: no table means no metrics yet. But the handler also returns [] for ACCESS_DENIED, a syntax error or an internal error.

ensure_monitoring_tables in the same file already draws this line. It accepts COLUMN_ALREADY_EXISTS and raises everything else, and test_ensure_monitoring_tables_raises_on_permission_error pins that.

An empty list has real consequences in the callers:

• MonitoringService calls _ensure_monitoring_tables() right before querying, so on that path the table exists and the handler only ever hides real errors behind an empty result.
• DQMJobManager.get_job returns None for [], and update_status returns early when the job is None. A failed read while marking a job running, completed or failed drops the status update without an error, and the job stays in its old state.

Reproduction

A mocked client raising TrinoQueryError({"errorName": "ACCESS_DENIED", ...}), on master: query_monitoring_metrics(...) returns [] and nothing is raised. The same for SYNTAX_ERROR and GENERIC_INTERNAL_ERROR.

Change

TABLE_NOT_FOUND and SCHEMA_NOT_FOUND still return [], since either means the monitoring table has not been created yet. Any other TrinoQueryError is logged and re-raised, the same as in ensure_monitoring_tables.

Verification

Two new tests in test_trino_monitoring.py. One covers SCHEMA_NOT_FOUND returning []. The other, parametrized over ACCESS_DENIED, SYNTAX_ERROR and GENERIC_INTERNAL_ERROR, checks that the error is raised. On master the 3 parametrized cases fail and the 2 not-found cases pass, including the existing TABLE_NOT_FOUND test. With the change, the Trino offline store tests are 28 passed. ruff check and ruff format --check are clean.

Which issue(s) this PR fixes:

None filed. The reproduction is above. This follows the Trino monitoring support added in #6779.

Checks

• I've made sure the tests are passing.
• My commits are signed off (git commit -s)
• My PR title follows conventional commits format

Testing Strategy

• Unit tests
• Integration tests
• Manual tests
• Testing is not required for this change