[Feature Request]: Support CAST AS XML clickable results in SQL Notebook outputs

Nobody has claimed this yet.

### Feature Description

I would like SQL Notebook code cell outputs to support the `CAST AS XML` behavior available in standard .sql execution, where XML results are rendered as clickable links that open the full content in a separate tab or viewer.

This pattern is commonly used to condense complex or nested query results into a single row while retaining the ability to drill into full details. Enabling this in notebooks would allow the same efficient querying and result exploration workflows currently available in .sql files.

_Alternative/ideal solution_ might be to completely replicate the query result panel functionality from a .sql file in .ipynb notebooks (same formatting, xml functionality, Ctrl⇧R to toggle display).

**Desired behavior examples:**

### Problem and Motivation

Currently, SQL Notebook code cells do not support the same result behaviors as standard .sql query execution, specifically the ability to interact with CAST AS XML outputs as clickable links that open full results in a separate view.

This limitation prevents the use of a long-standing and highly effective pattern for condensing complex or nested query results into a single row with drill-down capability. As a result, workflows that rely on exploring large or hierarchical datasets become less efficient within notebooks, often requiring a switch back to .sql files to inspect results properly.

With this feature, SQL Notebook outputs would support clickable XML result handling consistent with the standard SQL editor. This would preserve established querying patterns, enable efficient exploration of nested data directly within notebooks, and bring the notebook experience in line with the existing .sql workflow, and the functionality in (now deprecated) Azure Data Studio.

### Related Area

- [ ] Connection dialog (SQL Server | Azure browse/Fabric browse)
- [ ] Query editor
- [x] Query results panel
- [ ] Object Explorer
- [ ] GitHub Copilot integration
- [ ] Preview/Edit data
- [ ] Table Designer
- [ ] Schema Designer
- [ ] Schema Compare
- [ ] Local SQL Server Container provisioning
- [ ] SQL database in Fabric provisioning
- [ ] DACPAC/BACPAC export/import
- [ ] SQL Database projects
- [ ] Query Plan Visualizer
- [x] Other (please describe below)

### If you selected "Other", please describe the area

The output of code cells inside SQL Notebooks. This is apparently different than the Query Results panel in a standard .sql execution.

### Confirmation

- [x] I have searched existing feature requests and couldn't find a match
- [ ] I want to help implement this feature

No files or tests are named in the issue. Start by comparing standard .sql query-results handling with SQL Notebook code-cell output, focusing on the existing query results panel entry points. Done means CAST AS XML results in notebooks are clickable and open their full content in a separate view, matching the standard .sql workflow.

Written by the indexing model from the issue text.