fix: cosmwasmpool state export

[czarcas7ic]

Closes: #XXX

What is the purpose of the change

When serializing into the any codec type, we were previously utilizing GetPools, which utilized the Pool interface in the cosmwasmpool module. This interface includes a wasmkeeper field which cannot be serialized.

For purposes of import/export logic, we need a separate method that allows us to serialize the pools without this field.

This PR adds a GetPoolsSerializable method that serializes into the CosmwasmPool interface instead of the Pool interface. This gives us all the information we need for importing and exporting.

Testing and Verifying

Ran a state export on the cosmwasmpool module only, here is an excerpt, implying it works:

{
  "app_hash": "",
  "app_state": {
    "cosmwasmpool": {
      "params": {
        "code_id_whitelist": [
          "148"
        ],
        "pool_migration_limit": "20"
      },
      "pools": [
        {
          "@type": "/osmosis.cosmwasmpool.v1beta1.CosmWasmPool",
          "code_id": "148",
          "contract_address": "osmo15ns40n0pctl80d7l7praluufcywderupvgcl8xjg4gzvvhgv4vqq78vk7n",
          "instantiate_msg": "eyJwb29sX2Fzc2V0X2Rlbm9tcyI6WyJ7cG9vbF9hc3NldF9kZW5vbXM6W2liYy84MjQyQUQyNDAwODAzMkU0NTdEMkUxMkQ0NjU4OEZEMzlGQjU0RkIyOTY4MEM2Q>
          "pool_id": "1175"
        },
        {
          "@type": "/osmosis.cosmwasmpool.v1beta1.CosmWasmPool",
          "code_id": "148",
          "contract_address": "osmo136f4pv283yywv3t56d5zdkhq43uucw462rt3qfpm2s84vvr7rrasn3kllg",
          "instantiate_msg": "eyJwb29sX2Fzc2V0X2Rlbm9tcyI6WyJ7XCJwb29sX2Fzc2V0X2Rlbm9tc1wiOiBbXCJpYmMvRDE4OTMzNUM2RTRBNjhCNTEzQzEwQUIyMjdCRjFDMUQzOEM3NDY3N>
          "pool_id": "1176"
        },
        ...

Documentation and Release Note

• Does this pull request introduce a new feature or user-facing behavior changes?
• Changelog entry added to Unreleased section of CHANGELOG.md?

Where is the change documented?

• Specification (x/{module}/README.md)
• Osmosis documentation site
• Code comments?
• N/A

[czarcas7ic]

@devbot-wizard help

[czarcas7ic]

Highlighting that we had to implement this method, otherwise when we call SetPool in InitGenesis with a CosmWasmPool instead of a Pool, we need access to the GetId method. It should be fine to implement this though, since its defined on the CosmWasmPool struct and there is no need for the wasmkeeper to retrieve this.

[mattverse]

Nice, Can we add a test case for this? (specifically calling export genesis with cosmwasm pools)?

[czarcas7ic]

@mattverse added a test here dea8e71

reverted the change and confirmed test fails without this change