Require HrpIbcRecords to not contain the NativeHrp

[ChristianBorst]

It is my understanding the following situation is possible:
0. Osmosis mainnet has incorporated bech32ibc with "osmo" as the NativeHrp

1. A governance vote initiates and miraculously passes to add a HrpIbcRecord with Hrp = "osmo"
2. MsgSends are unaffected due to the bech32ics20 msg_server handling native transfers with the default bank handler

There are a couple avenues by which a chain could accept a confusing HrpIbcRecord containing the NativeHrp. It is important to note that the bech32ics20 current msg_server implementation would not allow an IBC transfer from the NativeHrp so this is not a critical issue.

However, the HrpIbcRecordProposalHandler should automatically fail any such proposal containing the NativeHrp to cancel any bad votes, and setHrpIbcRecord() should fail to store any such invalid proposal. The change to setHrpIbcRecord() would also cover the InitGenesis() path to this confusing state.