add back the API to take walrus module instead of wasm blob

[chenyan-dfinity]

Undo #19.

Decoupling walrus from ic-wasm API has the following drawbacks:

• We need walrus::ModuleConfig to control how we parse the Wasm module. Taking a blob from the API cannot customize the parsing option
• There are many use cases where we need to apply multiple transformations for the same Wasm module. With the blob API, we will have to re-parse the module several times
• To avoid importing walrus from the SDK, all we need are the two util functions to parse wasm blob into Module, as added in this PR