FxDAO test

[bbyalcinkaya]

This PR implements a simple FxDAO test contract and updates the test runner to support its execution.

Test Contract

The test contract has the following endpoints:

1. init: Takes a hash: Bytes as an argument, deploys a new FxDAO/vaults contract using this hash, and calls its init function. The FxDAO contract Wasm module must already be registered with this hash.
2. test_deposit_ratio: Calls the FxDAO contract that was deployed during the init function.
3. test_get_core_state: Calls the FxDAO contract’s get_core_state endpoint to retrieve and verify the contract state.

Test Runner Updates

The test runner has been updated to support init functions and the deployment of child contracts, such as FxDAO.

If the test involves a child contract, a kasmer.json config file should be present in the root directory of the test contract. This config file lists the paths to the Wasm files for the child contracts. Upon deploying the test contract, the child contract Wasm modules are automatically registered using uploadWasm.

If the test contract has an init function, it will be called with the hashes of the uploaded Wasm modules as arguments.

With these updates, the FxDAO test runs in the following steps:

1. Deploy the test contract.
2. Upload the FxDAO Wasm module using uploadWasm.
3. Call the test contract's init function with the hash used in step 2.
4. Call test_deposit_ratio with random or symbolic input.

[bbyalcinkaya]

For now, child contracts need to be precompiled. Maybe in a future PR, I can add a compilation step for child contracts.

[gtrepta]

Aside from the merge conflicts, looks good.