chore(target_chains/sui): add new chain ids for new networks

Author: ali-behjati

governance/xc_admin/packages/xc_admin_common/src/chains.ts

@@ -232,6 +232,7 @@ export const RECEIVER_CHAINS = {
   bittensor_testnet: 50115,
   monad_devnet: 50116,
   monad_testnet: 50117,
+  iota_sui_testnet: 50118,
 };
 
 // If there is any overlapping value the receiver chain will replace the wormhole

target_chains/sui/vendor/README.md

@@ -1,8 +1,8 @@
 # Vendored dependencies for SUI contract
 
-This directory contains the wormhole dependencies used for deploying Pyth contracts on the chains
-that Wormhole is not officially deployed on. For each network, a slightly different variant of the
-code should be used that has the `CHAIN_ID` and `Move.toml` modified. Therefore, we are storing
+This directory contains the wormhole dependencies used for deploying Pyth contracts on the chains that Wormhole is not
+officially deployed on. For each network, a slightly different variant of the code should be used that has the
+`CHAIN_ID` constant (in `wormhole/sources/state.move`) and `Move.toml` modified. Therefore, we are storing
 each of them in a separate directory.
 
 The Wormhole contract is taken out of commit

target_chains/sui/vendor/wormhole_iota_testnet/wormhole/sources/state.move

@@ -42,7 +42,7 @@ module wormhole::state {
     const E_INVALID_BUILD_DIGEST: u64 = 1;
 
     /// Sui's chain ID is hard-coded to one value.
-    const CHAIN_ID: u16 = 50076;
+    const CHAIN_ID: u16 = 50118;
 
     /// Capability reflecting that the current build version is used to invoke
     /// state methods.