restructure supported networks & add Mock contracts

Author: khadni

reports/llms-report.json

@@ -1,22 +1,22 @@
 {
-  "startedAt": "2025-11-19T17:59:11.211Z",
+  "startedAt": "2025-11-20T16:39:09.670Z",
   "siteBase": "https://docs.chain.link",
   "sections": [
     {
       "section": "cre-go",
-      "pagesProcessed": 84,
+      "pagesProcessed": 81,
       "outputPath": "src/content/cre/llms-full-go.txt",
-      "bytes": 634954,
-      "prevBytes": 634936,
-      "deltaBytes": 18
+      "bytes": 638965,
+      "prevBytes": 634954,
+      "deltaBytes": 4011
     },
     {
       "section": "cre-ts",
-      "pagesProcessed": 79,
+      "pagesProcessed": 76,
       "outputPath": "src/content/cre/llms-full-ts.txt",
-      "bytes": 590375,
-      "prevBytes": 590357,
-      "deltaBytes": 18
+      "bytes": 594472,
+      "prevBytes": 590375,
+      "deltaBytes": 4097
     },
     {
       "section": "vrf",
@@ -123,5 +123,5 @@
       "deltaBytes": 0
     }
   ],
-  "finishedAt": "2025-11-19T17:59:15.575Z"
+  "finishedAt": "2025-11-20T16:39:13.887Z"
 }

src/content/cre/guides/workflow/using-evm-client/onchain-write/building-consumer-contracts.mdx

@@ -318,13 +318,15 @@ When you run `cre workflow simulate`, your workflow interacts with a **`MockKeys
 
 ### Forwarder address validation
 
-You **can** configure the forwarder address check during simulation:
+You **can** configure the forwarder address check during simulation using the **Mock Forwarder Address**:
 
 ```solidity
-// Optional: Validate the MockKeystoneForwarder address during simulation
-myConsumer.setForwarderAddress(0xMockForwarderAddress);
+// Example: Use Mock Forwarder for Ethereum Sepolia simulation
+myConsumer.setForwarderAddress(0x15fC6ae953E024d975e77382eEeC56A9101f9F88);
 ```
 
+Find Mock Forwarder addresses for all networks in the [Supported Networks](/cre/guides/workflow/using-evm-client/supported-networks) page.
+
 {/* prettier-ignore */}
 <Aside type="caution" title="Important: Different addresses for simulation vs production">
   The `MockKeystoneForwarder` address used during simulation is **different** from the `KeystoneForwarder` address used by deployed workflows. If you configure the forwarder address for simulation, remember to update it to the production `KeystoneForwarder` address after deploying. See [Supported Networks](/cre/guides/workflow/using-evm-client/supported-networks) for forwarder addresses.