Add warnings when provider unbonding is shorter than consumer unbonding

[p-offtermatt]

Description

Changes the client code for creating consumer addition proposals so that a warning is printed when
the unbonding period in the proposal is >= than the unbonding period of the provider.

To test anything here, I needed to create a mock of the CometBFT RPC client. I didn't find anything like this elsewhere, but lmk if it already exists.

For the error message, I don't think the logger in the app is in scope here, so I just print to stderr.

Linked issues

Closes: #733

Type of change

If you've checked more than one of the first three boxes, consider splitting this PR into multiple PRs!

• Feature: Changes and/or adds code behavior, irrelevant to bug fixes
• Fix: Changes and/or adds code behavior, specifically to fix a bug
• Refactor: Changes existing code style, naming, structure, etc.
• Testing: Adds testing
• Docs: Adds documentation

New behavior tests

Added a test for the logic that checks unbonding periods of provider and consumer against each other.

Versioning Implications

• This PR will affect semantic versioning as defined for ICS

If the above box is checked, which version should be bumped?

• MAJOR: Consensus breaking changes to both the provider and consumers(s), including updates/breaking changes to IBC communication between provider and consumer(s)
• MINOR: Consensus breaking changes which affect either only the provider or only the consumer(s)
• PATCH: Non consensus breaking changes

Targeting

Please select one of the following:

• This PR is only relevant to main
• This PR is relevant to main, and should also be back-ported to ____ (ex: v1.0.0 and v1.1.0)
• This PR is only relevant to ____ (ex: v1.0.0, v1.1.0, and v1.2.0)

[p-offtermatt]

The quality gate is a bit unhelpful here: The new code is in an area where we have 0% test coverage at the moment, since it is concerned with the CLI, for which there are no unit tests. I added tests for my new functionality as much as possible. I'm not sure how to cover more code here, but am open to suggestions. Alternatively, we can ignore the code coverage for this one.

[p-offtermatt]

Summary of changes since the reviews:

• I get the proper unbonding time from the staking module now, rather than the max evidence age.
• I removed the test for the functionality, since I needed to call a different client to get the proper unbonding time, so my mock was also obsolete. My reasoning for the removal is that we do not test for CLI interactions at the moment at all. I think doing CLI unit testing properly is out of the scope of this PR, and is maybe something we do not need to do at all, since we have e2e tests that call the cli. My test before was too focused on my implementation, rather than the expected behavior, as seen by the fact that changing the implementation slightly would need a complete rewrite of the test.

[MSalopek]

New changes look good.

Approve!

[shaspitz]

One comment but LGTM!