[BUG] WASM contract initialization process

[yun-yeo]

Describe the bug
In current context, the contract initialize step is as follow

1. Call init function of a contract
2. Dispatch all response messages from the init of the contract
3. Store the contract info to store

so the response messages cannot use the initialized contract like post initialization.
Ex)
Let's assume
A contract A is creating a contract B at init function and the contract B is invoking the contract A to register itself at init function.

Then it must be failed in current initialization process, because the initialized contract A is not store until the all response messages(create the contract B and invoke the contract A to register the contract B) are fully finished. The response messages cannot invoke the contract A.

To Reproduce
Try to use the initialized contract at initialization step with response messages.

Context & versions
v0.4.0-rc.4

(if applicable) suggested solution
Store the initialized contact data first before dispatching response messages.