fix: store key uniqueness

[robert-zaremba]

Description

While reviewing the module store keys and app wiring I notice that we don't correctly check for collisions, which can happen when:

1. There are 2 modules use the same key (in fact this is a special case of the next one)
2. There are 2 store keys, such that, one key is a prefix of another

It's also not clear to me why we need all this different types:

StoreKey, CapabilityKey, KVStoreKey, TransientStoreKey, MemoryStoreKey

They don't really protect against collision, neither pointers - because modules will reference store keys by name.

PS: I didn't create an issue - just went ahead and updated the code.

---

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

[robert-zaremba]

so, StoreKey, CapabilityKey, TransientStoreKey, MemoryStoreKey (all except KVStoreKey) are not needed now, but could be useful for declaring module dependencies.

[technicallyty]

LGTM