Remove no shell integration warning (#8749)

It's being removed due to microsoft/vscode#260880 in candidate fix
microsoft/vscode#261206

Author: Tyriar

release-notes/images/1_103/terminal-chat-si-none.png

@@ -176,14 +176,6 @@ We're gradually rolling out support for this feature on the services side, so no
 
 We have migrated the tools for running tasks and commands within the terminal from the Copilot extension into the core [microsoft/vscode repository](https://github.com/microsoft/vscode). This gives the tools access to lower-level and richer APIs, allowing us to fix many of the terminal hanging issues. This update also comes with the benefit of more easily implementing features going forward, as we're no longer restricted to the capabilities of the extension API, especially any changes that need custom UI within the Chat view.
 
-### Warning about no shell integration when using chat
-
-While we strive to allow agent mode to run commands in terminals without shell integration, the experience will always be inferior as the terminal is essentially a black box at that point. Examples of issues that can occur without shell integration are: no exit code reporting and the inability to differentiate between a command idling and a prompt idling, resulting in output possibly not being reported to the agent.
-
-When the `run in terminal` tool is used but [shell integration](https://code.visualstudio.com/docs/terminal/shell-integration) is not detected, a message is displayed calling this out and pointing at the documentation.
-
-![Screenshot of a message in the Chat view saying "Enable shell integration to improve command detection".](images/1_103/terminal-chat-si-none.png)
-
 ### Output polling for tasks and terminals
 
 The agent now waits for tasks and background terminals to complete before proceeding by using output polling. If a process takes longer than 20 seconds, you are prompted to continue waiting or move on. The agent will monitor the process for up to two minutes, summarizing the current state or reporting if the process is still running. This improves reliability when running long or error-prone commands in chat.