chore: remove duplicate imports

[damiannolan]

Description

• Cleanup import aliases in ICS27 msg_server_test.go

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.
• Wrote unit and integration tests
• Updated relevant documentation (docs/) or specification (x/<module>/spec/)
• Added relevant godoc comments.
• Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
• Re-reviewed Files changed in the Github PR explorer
• Review Codecov Report in the comment section below once CI passes

[chatton]

if we have icatypes, clienttypes channeltypes etc. does it make sense to have a package imported as just types? It's not immediately obvious which sort of types it is, I would lean in favour of keeping it called controllertypes and removing the unaliased one WDYT?

[damiannolan]

In a lot of other packages we normally import the relative types pkg as is, and then for any types pkgs from other modules we alias them.

I don't really feel strongly about it here. It's also a test file so.. 🤷

[damiannolan]

For interchain accounts it may help to always alias tho. Considering there is the shared icatypes and then a separate types for both controller and host submodules

[chatton]

ah I see okay, so we generally just do external types with the alias, that seems fine with me 👍