Investigate how best to expose errors to DAOs

[0xekez]

If a DAO executes a message via polytone, we should provide the same proposal close-on-execution-failure option as we do for normal messages. We should also make this error event visible to the DAO DAO indexer via queries.

[0xekez]

there is leeway in how we design this. i don't think we are married to returning an unlabeled binary blob. developer UX is most important here.

also, two notes from conversation with larry and ethan

1. the error string is not stored in the merkle tree, so the error fields in our callbacks will be the classic "codespace wasm: 5".
2. the attributes of the CosmWasm reply only contain attributes from x/wasm as they had to remove the rest due the SDK being non-deterministic.

[Art3miX]

We should return what we can and need, this ensures that if updates are made to the returned data, we pretty much get it for "free" (closest to free we can get them).
I think #19 is doing it right, its feels like you get a direct response from your sent msgs.

[0xekez]

closing for #19