[Aegis] Separate sections for fetch and connect in workers.mdx (#24121)

* Create separate sections for fetch and connect

* Disambiguate whenever and use Aegis IPs throughout

* Apply suggestions from code review

Co-authored-by: Jun Lee <[email protected]>

---------

Co-authored-by: Jun Lee <[email protected]>

Author: RebeccaTamachiro

src/content/docs/aegis/configuration-options/workers.mdx

@@ -9,8 +9,14 @@ head:
 
 [Workers](/workers/) provides a serverless execution environment for you to create applications leveraging Cloudflare's global network.
 
-When paired with Aegis, whenever Cloudflare's developer platform needs to access services on your origin, it will use the dedicated IP addresses.
+Refer to the sections below for information on how Aegis pair up with Workers.
 
-:::note
-For Workers subrequests — meaning requests from one Worker to another — it is expected that different IPs are used. However, requests to external origins made by a Worker invoked via a subrequest will use the dedicated IP addresses.
-:::
+## `fetch`
+
+[`fetch()` requests](/workers/runtime-apis/fetch/) that access services on your origin will use Aegis IP addresses.
+
+Workers subrequests — requests from one Worker to another — are expected to use different IPs. However, [`fetch()` requests](/workers/runtime-apis/fetch/) to external origins made by a Worker invoked via a subrequest will use Aegis IP addresses.
+
+## `connect`
+
+For [`connect()` requests](/workers/runtime-apis/tcp-sockets/) - which create outbound TCP connections from Workers - Aegis IPs are **not** used.