enforce calls to ics27 message server to not route through underlying app callbacks in ics27 controller

[colin-axner]

Summary

Legacy calls to SendTx and RegisterInterchainAccount should route through the underlying app, while calls to the message server should not

Problem Definition

Calls through the message server may not want the underlying app to handle their packet (the underlying app did not send the packet nor register the account).

Proposal

Add a mapping which sets a flag ([]byte(1) similar to core IBC receipt)) if the underlying app is created with the legacy API or the new API. A new registerInterchainAccount function has been added, so this can be extended with a boolean

Every call to the underlying app should be associated with a lookup to whether the channel should use the underlying app or not

This is backwards compatible (previous functionality remains unchanged) and can be removed in the future when we remove the underlying app from ics27 controller

---

For Admin Use

• Not duplicate issue
• Appropriate labels applied
• Appropriate contributors tagged/assigned