Improved error messages for client state/consensus queries

[adizere]

Closes: #XXX

Description

While debugging with a relayer operator this log message:

Jan 20 02:43:40 Imperator-Relayer hermes[751041]: 2022-01-20T02:43:40.107723Z WARN ThreadId(73) task RefreshClientWorker(sentinelhub-2 -> osmosis-1:07-tendermint-645) encountered ignorable error: failed while querying Tx for client 07-tendermint-645 on chain id: osmosis-1: error decoding protobuf: error converting message type into domain type: the client state was not found

We found out that Hermes logs generic messages and we cannot debug without additional refinement on the error types of ForeignClient. This PR addresses that.

---

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).

[adizere]

Thanks for the review & approval Mikhail. I'll go ahead and merge this, since it's a simple one that improves debugging & observability.

For reference, the problem the operator was having was that he had filter = false, so Hermes spawned client refresh tasks for many (even expired) clients. In particular, the refresh task for client 07-tendermint-645 on osmosis-1 was failing because the latest_height for this client was 2-2551351. Sentinel produced that block 4 months ago , and probably Osmosis pruned the client's state, hence Hermes was failing the query for the client consensus state at that height.