imp!: allow failure expectations when using chain.SendMsgs

[damiannolan]

Description

Allow failure expectations from function calls which use chain.SendMsgs()

e.g. I want to be able to call endpoint.ChanUpgradeInit() and expect an error is returned

• Removes testing.TB and expPass args from SignAndDeliver and allows the caller to determine whether or not the expectation is success or failure.

closes: #XXXX

---

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

• Targeted PR against correct branch (see CONTRIBUTING.md).
• Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
• Code follows the module structure standards and Go style guide.
• Wrote unit and integration tests.
• Updated relevant documentation (docs/) or specification (x/<module>/spec/).
• Added relevant godoc comments.
• Provide a commit message to be used for the changelog entry in the PR description for review.
• Re-reviewed Files changed in the Github PR explorer.
• Review Codecov Report in the comment section below once CI passes.

[DimitrisJim]

+1 looks like a good idea to me

[chatton]

LGTM 🙏

[charleenfei]

nice idea, sgtm!

[colin-axner]

Just a note this will be reconfigured in the update to Eden, but the same concept is applied. If the tx returns a non-zero error code, it will be returned as an error to the SendMsgs caller