Dynamically detect CW pool code ID migrations

[p0mvn]

Currently, we still sometimes experience issues when cw pools migrate despite adding fault tolerance.

As one of the approaches to mitigate, we should detect cw pool migrations via SDK state-streaming and push them into SQS, replacing code ID in the config.

There are multiple approaches we could pursue:

1. Write a state entry migration in chain state and then delete it to trigger state-streaming. Dynamically update SQS
2. Do transaction/message parsing (expensive)
3. Monitor wasmd state migrations (complex)

Proposing option 1 as the migrations are not expected to be triggered frequently, and we will clean up the state while triggering the necessary component.

This would also simplify the architecture as a whole

As part of this effort, we will have to synchronize the cosmwasm pool config with a read-write lock.

DoD

• Add logic to update a migration state-entry
• Dynamically propagate it to SQS ingest
• Syncronize and update the cosmwasm code id config
• Unit test
• Locally test against mainnet state