EPIC: cosmwasm frameworks should be easily deployable via interchaintest

[Reecepbcups]

Ppl building on CW
Want to easily be able to deploy complex setup envs via interchaintest as a one-liner
Because it aligns the right thing to do w/ the easy thing to do (and save them—and Future Us—tens of hours)

---

Common CW frameworks should be easier to setup & interact with in interchaintest

Beta Give feedback

1. ICT should be able to automatically use the Abstract SDK #1136
   +0
   
2. ICT should be able to automatically use Mesh Security #1137
   +0
   
3. ICT should be able to automatically use Polytone contracts #1134
   +0
   
4. ICT should be able to automatically use DAODAO contracts #1135
   +0
   
5. ICT should be able to autonmatically use Valance contracts

---

Idea

A user should launch a new chain. After it starts and is running, a single line add of cwabstract := chain.GetNode().SetupAbstractSDK(options ...Opts) which will then setup the cosmwasm contracts for abstract on the chain. (Opts example. It's like a builder pattern)

Contracts can either be auto downloaded from the github CI & cached for the user, or we can keep hard coded contracts/ folder. Must have a README.md w/ where the files are and the version upstream (or commit)

Further, interaction would be very nice within for exec & queries: i.e. cwabstract.myInteractionMethod(...). This would just wasm execute under the hood. Similar to BankSend and others

Tasks

Beta Give feedback

No tasks being tracked yet.

[jonathanpberger]

Development is paused as @kakucodes is working on other projects. Returning to backlog.