Add code space information in unknown SDK error

[soareschen]

Description

Follow up on #2266 to improve the error diagnostic for unknown errors coming from Cosmos SDK by including the code space for the error. This should help us identify the source of error in Cosmos SDK or ibc-go, and better format the error message in Hermes.

---

PR author checklist:

• Added changelog entry, using unclog.
• Added tests: integration (for Hermes) or unit/mock tests (for modules).
• Linked to GitHub issue.
• Updated code comments and documentation (e.g., docs/).

Reviewer checklist:

• Reviewed Files changed in the GitHub PR explorer.
• Manually tested (in case integration/unit/mock tests are absent).

[soareschen]

It seems like the type tendermint_rpc::endpoint::broadcast::tx_sync::Response do not contain any code space information to help us correctly identify where the error code is coming from. The most common error we get inside integration tests looks like:

ERROR send_tx_with_account_sequence_retry{id=ibc-1-9e762a0c}: ibc_relayer::chain::cosmos::retry: broadcast_tx_sync: Response { code: Err(22), data: Data([]), log: Log("packet messages are redundant"), hash: transaction::Hash(053E3D4023EB1A90F3ADAC61FBAA58AA978804F9B5C662C080FD86270082125F) }: diagnostic: unknown TX sync response error: 22

The error seems to come from the ibc-go channel module. But without the code space information, it is not sufficient to determine if the error code 22 is really from the "channel" code space.

[adizere]

The most common error we get inside integration tests looks like:
ERROR send_tx_with_account_sequence_retry{id=ibc-1-9e762a0c}: ibc_relayer::chain::cosmos::retry: broadcast_tx_sync: Response { code: Err(22), data: Data([]), log: Log("packet messages are redundant"), hash: transaction::Hash(053E3D4023EB1A90F3ADAC61FBAA58AA978804F9B5C662C080FD86270082125F) }: diagnostic: unknown TX sync response error: 22

FYI this is the bug that @seanchen1991 is trying to tackle here: #2256