Add IBC module level errors

[chatton]

Description

part of: #2896

This PR duplicates the errors found here and uses the ibc as the module name. They will be used in a follow up PR.

Commit Message / Changelog Entry

N/A

see the guidelines for commit messages. (view raw markdown for examples)

---

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.

[damiannolan]

What do you think about assigning the ibc module name to a codespace constant and using that in the calls to Register?

const codespace = exported.ModuleName

[chatton]

What do you think about assigning the ibc module name to a codespace constant and using that in the calls to Register?

const codespace = exported.ModuleName

don't feel strongly either way! Happy to make this change if you think it makes things clearer

[colin-axner]

Looks great to me. Thanks @chatton 🙂

[damiannolan]

Will be great to have deprecation warnings gone after this migration! Thanks ❤️