fix(cli): warp send relevant chains (#8355)

Co-authored-by: devin-ai-integration[bot] <158243242+devin-ai-integration[bot]@users.noreply.github.com>

Author: troykessler

.changeset/popular-readers-film.md

@@ -0,0 +1,5 @@
+---
+"@hyperlane-xyz/cli": patch
+---
+
+Only loaded relevant chains for warp send command, improving performance by avoiding loading all chain configurations.

typescript/cli/src/send/transfer.ts

@@ -19,6 +19,7 @@ import {
   assert,
   parseWarpRouteMessage,
   timeout,
+  pick,
 } from '@hyperlane-xyz/utils';
 
 import { EXPLORER_URL } from '../consts.js';
@@ -186,9 +187,16 @@ async function executeDelivery({
   }
 
   const chainAddresses = await registry.getAddresses();
+  const filteredChainAddresses =
+    origin && destination
+      ? pick(chainAddresses, [origin, destination])
+      : chainAddresses;
 
   // Core is needed for on-chain wait (EVM destinations)
-  const core = HyperlaneCore.fromAddressesMap(chainAddresses, multiProvider);
+  const core = HyperlaneCore.fromAddressesMap(
+    filteredChainAddresses,
+    multiProvider,
+  );
 
   // Extract mailbox addresses from registry for each chain
   // Required for Sealevel/non-EVM token adapters during validation