Contract interfaces generated by "moonworm generate" should coerce types before web3 calls

[zomglings]

An example error we saw in Moonstream Engine API:

Before:

            message_hash = dropper_contract.claimMessageHash(
                claimant_drop.claim_id,
                claimant_drop.address,
                claimant_drop.claim_block_deadline,
                transformed_amount,
            ).call()

Error:

web3.exceptions.ValidationError:                                                                                                                                                    
Could not identify the intended function with name `claimMessageHash`, positional argument(s) of type `(<class 'int'>, <class 'str'>, <class 'int'>, <class 'str'>)` and keyword argument(s) of type `{}`.                                                                                                                                                              
Found 1 function(s) with the name `claimMessageHash`: ['claimMessageHash(uint256,address,uint256,uint256)']                                                                         
Function invocation failed due to no matching argument types.

After:

            message_hash = dropper_contract.claimMessageHash(
                claimant_drop.claim_id,
                claimant_drop.address,
                claimant_drop.claim_block_deadline,
                int(transformed_amount),
            ).call()

This is not an issue with the moonworm generate-brownie interfaces because I believe brownie does the type coercion before making the web3 call.

It would be useful if we did this ourselves in the generated classes for moonworm generate.

[zomglings]

Maybe there is a way to configure web3 client to coerce to ABI types without us having to do it ourselves?