…2449)

…2465)

### What
Add SHA-256 integrity verification to `get_remote_wasm_from_hash` in
`utils::rpc`. After fetching Wasm bytecode, compute
`sha256(returned_bytes)` and compare it to the requested hash. Return a
clear error with both the expected and computed hashes if they don't
match. Add unit tests for matching and mismatched hashes.

### Why
The CLI fetched WASM bytecode from RPC servers without verifying the
returned bytes matched the requested hash. While most data is trusted
from the connected RPC, it's good defensive approach if the CLI verifies
the contract code because it gets cached against the hash for future use
locally.

Close #2463

### What

Add a confirmation prompt when deleting keys. The confirmation prompt
can be bypassed with a `--force` flag. Confirmation also works by piping
`y` into `stdin`.

```bash
$ stellar keys rm rmtest           
⚠️  Are you sure you want to remove the key 'rmtest' at '/my-config-path/.config/stellar/identity/rmtest.toml'? This action cannot be undone. (y/N)
y
ℹ️  Removing the key's cli config file
```

```bash
$ stellar keys rm rmtest --force          
ℹ️  Removing the key's cli config file
```

```bash
$ stellar keys rm rmtest      
⚠️  Are you sure you want to remove the key 'rmtest'? This action cannot be undone. (y/N)
N
❌ error: removal cancelled by user
```

### Why

Closes: #2420 

### Known limitations

None

---------

Co-authored-by: Nando Vieira <me@fnando.com>

### What

Handle other types when printing values using xdr_to_json.

### Why

Fix #2469.

### Known limitations

[TODO or N/A]

---------

Co-authored-by: mootz12 <38118608+mootz12@users.noreply.github.com>