Fix IOTA-SUI folder mismatch and restore correct structure in 'target_chains'

[pavlo-u]

Summary

This PR resolves a folder mismatch issue in target_chains where the sui folder was overwritten with IOTA code. It:

• Renames the current target_chains/sui folder (which contained IOTA code) to target_chains/iota to place the IOTA code in its proper directory.
• Restores the original target_chains/sui folder from a previous commit to bring back Sui support.
• Ensures IOTA and Sui have separate, correctly named directories within target_chains.

Rationale

The recent IOTA integration replaced the target_chains/sui folder with IOTA code instead of creating a dedicated target_chains/iota folder. This broke Sui support and misplaced IOTA code in the sui directory, where it didn’t belong. These changes are necessary to restore Sui functionality and relocate IOTA code to its intended location, maintaining proper separation of blockchain-specific code under target_chains.

How has this been tested?

• Current tests cover my changes
• Added new tests
• Manually tested the code

I manually verified the changes by:

1. Confirming the target_chains/iota folder now contains the IOTA-specific code, correctly relocated from sui.
2. Confirming the target_chains/sui folder contains the restored Sui-specific code from commit <commit-hash> (replace with the actual hash).
3. Checking that the folder structure under target_chains now correctly separates IOTA and Sui dependencies in their respective directories.

Note: If there are existing tests for Sui and IOTA integrations within target_chains, I recommend running them to ensure no regressions. I didn’t add new tests as this is a structural fix, but please advise if the tests need updating.

[vercel]

@pavlo-u is attempting to deploy a commit to the Pyth Network Team on Vercel.

A member of the Team first needs to authorize it.