Hermes should retry on TxNoConfirmation error

[ancazamfir]

Crate

relayer

Summary of Bug

hermes should retry below on TxNoConfirmation (in addition to the retry for ChainError further down)
https://github.com/informalsystems/ibc-rs/blob/d41f7fa5c0923ebcd5e3c8f62ec469ad5b1c335f/relayer/src/link.rs#L742

Version

v0.5.0, master

Steps to Reproduce

tbd, i expect if we make the number of retries for retrieving the Tx to something like 2 we should be able to reproduce this locally.
The problem was seen in a debug session for unrelayed packets on cosmoshub-4 - osmosis-1 channel. hermes start should have cleared the packets but after the TxNoConfirmation error it was giving up.

Acceptance Criteria

• add smoother retry mechanism to prevent missed packets
• fix error in log ERROR [cosmoshub-4] error during batch processing: missing chain for id (osmosis-1) in configuration file by filtering out batches (e.g., using a method on CollectedEvents) if their destination chain is not specified in the configuration file

---

For Admin Use

• Not duplicate issue
• Appropriate labels applied
• Appropriate milestone (priority) applied
• Appropriate contributors tagged
• Contributor assigned/self-assigned