Streaming long Markdown links repeatedly reflow tables

Describe the bug

While a response is streaming, inline Markdown links inside tables cause repeated table re-layout and visually disruptive jumping.

For a Markdown link such as [foo](https://very-long-url...) inside a table, the URL arrives character by character. Each character appears to trigger another table layout/render pass using the incomplete raw Markdown. The columns continuously resize and wrap; once the closing ) arrives, the whole link collapses to its visible text (foo) and the table jumps again.

This makes tables containing several long links very slow and visually unstable even though the final rendered table may look correct.

Affected version

GitHub Copilot CLI 1.0.77.

Steps to reproduce the behavior

1. Start GitHub Copilot CLI in interactive mode.

2. Enter this prompt:

   Render a Markdown table with several rows. Each row must contain an inline Markdown link whose destination URL is at least 150 characters long.

3. Watch the table while the response streams.

4. Observe columns repeatedly resizing and wrapping while each link destination arrives.

5. Observe another layout jump when each completed link collapses to its visible text.

Expected behavior

Streaming incomplete Markdown should not cause a full table re-layout on every character. Table columns should remain visually stable while link destinations stream, then render using the visible link text when complete.

Additional context

• OS: macOS 26.5.2
• CPU architecture: arm64
• Shell: zsh
• Video: https://github.com/user-attachments/assets/98bc24df-27e5-47f6-aab2-345dd3e995e2

The video uses a trivial example. The effect becomes much more disruptive with additional columns and rows. The demo also rendered unusually quickly; normal rendering is approximately 0.3-0.5 times this speed.

Comienza en la ruta de renderizado de tablas Markdown en streaming de interactive-mode y reproduce el problema con enlaces inline largos en varias filas de la tabla. Rastrea las pasadas de layout repetidas a medida que llegan los caracteres de la URL; el trabajo estará terminado cuando los enlaces incompletos ya no desencadenen remaquetaciones completas y disruptivas de la tabla, mientras que los enlaces completados se rendericen usando su texto visible.