[BUG] Snowflake: Inconsistent `TIMESTAMP_LTZ` handling with Core

**Describe the bug**
`dbt show` on TIMESTAMP_LTZ types is inconsistent between dbt Core and Fusion. TIMESTAMP_LTZ values are rendered as `offset` hours _behind_ the expected value (as if converting back to UTC), instead of reflecting the user/session local time.

**What version of dbt Fusion is this bug in? (find out by running `dbt --version`)**
preview.173

**Is this a discrepancy between the dbt Fusion Engine and dbt Core? Check one.**
- [x] YES
- [ ] NO

**To Reproduce**
Set user's Snowflake timezone to non-UTC timezone (e.g. `ALTER USER SET TIMEZONE = 'America/Los_Angeles';`).
Run `dbtf show --inline "SELECT sysdate() AS utc, CURRENT_TIMESTAMP() AS local, CAST(SYSDATE() AS TIMESTAMP_LTZ) AS utc_to_local"`

Observe incorrect output:
```
dbt-fusion 2.0.0-preview.173
Loading profiles.yml
Loading packages.yml
Query show_sql_operation_inline
┌─────────────────────────┬──────────────────────────┬──────────────────────────┐
│ UTC ┆ LOCAL ┆ UTC_TO_LOCAL │
╞═════════════════════════╪══════════════════════════╪══════════════════════════╡
│ 2026-04-28T15:57:03.691 ┆ 2026-04-28T15:57:03.691Z ┆ 2026-04-28T22:57:03.691Z │
└─────────────────────────┴──────────────────────────┴──────────────────────────┘
```
**Expected behavior**
Core output (aligns with runing query directly in Snowflake):
```
| UTC | LOCAL | UTC_TO_LOCAL |
| -------------------------- | -------------------------------- | -------------------------------- |
| 2026-04-28T15:59:19.053000 | 2026-04-28T08:59:19.053000-07:00 | 2026-04-28T15:59:19.053000-07:00 |
```

**Operating System and CPU Type (please complete the following information):**
* Windows x86