docs: move AI Transport cross-ref to SSE and pub-sub pages

Remove the shoehorned placement after the channel groups section
and add cross-references where developers are actively doing
something relevant: after the publish code examples on the pub-sub
page, and after the SSE advantages comparison.

Author: mattheworiordan

src/pages/docs/channels/index.mdx

@@ -230,7 +230,3 @@ Ably does not support channel groups, a concept used by some other providers whe
 * Channel namespaces already provide grouping functionality for configuration purposes.
 
 Instead of channel groups, simply subscribe to the specific channels your client needs access to. The efficient multiplexing ensures optimal performance regardless of the number of channels.
-
-<Aside data-type='further-reading'>
-If you are building AI-powered applications that stream LLM responses to users, [AI Transport](/docs/ai-transport) provides purpose-built features for token streaming, session management, and human-in-the-loop workflows on top of Ably channels.
-</Aside>

src/pages/docs/protocols/sse.mdx

@@ -38,6 +38,10 @@ SSE is an excellent alternative to Ably SDK in memory-limited environments.
 * Access to a comprehensive range of features including, but not limited to, [publishing](/docs/push/publish), [presence](/docs/presence-occupancy/presence), [history](/docs/storage-history/history), [push notifications](/docs/push), [automatic payload encoding](/docs/channels/options/encryption), and [symmetric encryption](/docs/channels/options/encryption).
 * Optimal compatibility with browsers via the WebSocket protocol.
 
+<Aside data-type="note">
+If you are streaming LLM responses to users, [AI Transport](/docs/ai-transport) provides purpose-built token streaming with resumable sessions and multi-device continuity, addressing the limitations of HTTP-based streaming.
+</Aside>
+
 ## Configuration <a id="config"/>
 
 The following code sample provides an example of how to use SSE with Ably:

src/pages/docs/pub-sub/index.mdx

@@ -438,6 +438,10 @@ if err := channel.Publish(context.Background(), "example", "message data"); err
 </Code>
 
 
+<Aside data-type="note">
+If you are publishing messages to stream LLM responses to users, [AI Transport](/docs/ai-transport) provides purpose-built token streaming with resumable sessions, multi-device continuity, and human-in-the-loop workflows on top of pub-sub.
+</Aside>
+
 <Aside data-type="further-reading">
 You can find out more detail about how [channels](/docs/channels) and [messages](/docs/messages) work.