feat: Add a stellar contract info wasm-hash command

[Dhanraj30]

What

Closes: #1877
This PR adds a new command wasm-hash to the stellar contract CLI, allowing developers to retrieve the Wasm hash of a deployed contract directly from the command line.

Why

Currently, developers have to rely on more complex methods, such as using RPC calls or parsing logs, to obtain the Wasm hash of a contract. This new command simplifies the process, making it more convenient and efficient for developers to access the Wasm hash directly. It enhances the usability of the CLI by providing a straightforward command that outputs the hash in a format suitable for scripting and automation.

Get the Wasm hash of a deployed contract.

Usage

stellar contract wasm-hash --network <NETWORK> --contract-id <CONTRACT_ID>

Arguments

• --network: The network to use (e.g., testnet, futurenet, mainnet, or custom URL)
• --contract-id: The ID of the deployed contract to get the Wasm hash for

Example

# Get the Wasm hash for a contract on testnet
stellar contract wasm-hash --network testnet --contract-id CDSJWGUPY2HFHYNLT3EZX7YGJ4X7YMWPQWHHGNKB6IVH6WRXAJFI7627

# Output:
283f8e42a3585aa3a511c06c7d09a94d66762773cdf493cc4afc455d7b68adcf

Notes

• The contract must be deployed on the specified network
• The hash is returned in hexadecimal format
• The command requires a network connection to retrieve the contract data

[leighmcculloch]

👏🏻 This looks good, thanks for contributing.

There's a few small things that need fixing up. I've left comments inline on each.

The other thing this needs is an test. Tests that use commands and interact with an RPC are located in the following directory:

cmd/crates/soroban-test/tests/it

The way the tests work may not be intuitive because it's pretty bespoke. Let me know if that's something that you get stuck on.

Thanks again!