CLI Command to query connection channels

[adizere]

Closes: #505

Description

Added the following command:

rrly -c loop_config.toml query connection channels [CHAIN-ID] [CONNECTION-ID]

Sample outputs:

$ rrly -c loop_config.toml query connection channels ibc-0 connection-1
connection query result: []

$ rrly -c loop_config.toml query connection channels ibc-0 connection-0
connection query result: [ChannelId("channel-0")]

Error-prone cases:

$ rrly -c loop_config.toml query connection channels ibc-3 connection-0
error: invalid options: missing chain configuration for the given chain id

$ rrly -c loop_config.toml query connection channels ibc-3 connection-0
connection query error query error: GRPC error: transport error: error trying to connect: tcp connect error: Connection refused (os error 61)

Also offers option for json output (initial experience towards #500): (this work will take place in a different PR)

---

For contributor use:

• Updated the Unreleased section of CHANGELOG.md with the issue.
• If applicable: Unit tests written, added test to CI.
• Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
• Updated relevant documentation (docs/) and code comments.
• Re-reviewed Files changed in the Github PR explorer.

[codecov-io]

Codecov Report

Merging #506 (0076f0c) into master (b1b37f5) will increase coverage by 16.0%.
The diff coverage is 56.4%.

@@            Coverage Diff            @@
##           master    #506      +/-   ##
=========================================
+ Coverage    13.6%   29.7%   +16.0%     
=========================================
  Files          69     160      +91     
  Lines        3752   12917    +9165     
  Branches     1374    5092    +3718     
=========================================
+ Hits          513    3845    +3332     
- Misses       2618    8389    +5771     
- Partials      621     683      +62     

Impacted Files	Coverage Δ
...application/ics20_fungible_token_transfer/error.rs	0.0% <0.0%> (ø)
...pplication/ics20_fungible_token_transfer/events.rs	0.0% <ø> (ø)
...ion/ics20_fungible_token_transfer/msgs/transfer.rs	0.0% <0.0%> (ø)
modules/src/events.rs	0.0% <0.0%> (ø)
modules/src/ics02_client/events.rs	0.0% <0.0%> (ø)
modules/src/ics02_client/msgs.rs	0.0% <0.0%> (ø)
modules/src/ics02_client/raw.rs	0.0% <0.0%> (ø)
modules/src/ics03_connection/error.rs	13.6% <0.0%> (-19.7%)	⬇️
modules/src/ics03_connection/events.rs	0.0% <0.0%> (ø)
modules/src/ics04_channel/error.rs	75.0% <ø> (+50.0%)	⬆️
... and 283 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b324dc0...c51b814. Read the comment docs.

[adizere]

This should be ready for review. If you wish, @cezarad and @vitorenesduarte please also have a look over the PR and any thoughts or questions would be welcome!

[vitorenesduarte]

If there are any errors here, they will be silently ignored. Maybe we can instead do something like this: https://doc.rust-lang.org/rust-by-example/error/iter_result.html#fail-the-entire-operation-with-collect

[ancazamfir]

We can do this but the question is do we want to fail the entire operation if we cannot extract one ChannelId?

[adizere]

Good catch.

Between the option of failing the operation because an identifier fails to parse, and ignoring the offending identifier(s), I would rather go with the latter.

One middle-road solution is to have warnings in case some identifiers fail to parse. We're not (yet) principled with how we use warnings, if at all, so I'm adding a TODO here to keep an eye out in the future. c51b814

[ancazamfir]

Looks good! Thanks Adi!