feat: Prove contract inclusion with constructor args

[LHerskind]

The leaf in the contracts tree should include the constructor vk + args hash. That way ensuring that it can easily be used in factory setups.

Currently the pre-image of the leafs are (contract_address, portal_address, function_tree_root) which makes it difficult to figure out if the constructor was also the same as desired.

Why is this important? The functions might be the same, but if either the constructor or the arguments to it differs, it might set values differently to what was expected or other shenanigans.

[LHerskind]

To be done as part of larger restructure related to #3533.

[LHerskind]

Actually. The address of the contract is computed based on the deployer_public_key, contract_address_salt, function_tree_root and constructor_hash, where constructor_hash includes the constructor arguments and the constructor vk hash, so you could unwind that as well, allowing you do to it without making more changes to structs, but just throwing more data at it. Look in

aztec-packages/yarn-project/noir-protocol-circuits/src/crates/private-kernel-lib/src/common.nr

Lines 298 to 306 in 7c8814e

	if is_contract_deployment {
	//TODO(https://github.com/AztecProtocol/aztec-packages/issues/3062) use locally computed private_call_vk_hash here
	let constructor_hash = compute_constructor_hash(function_data, private_call_public_inputs.args_hash, contract_dep_data.constructor_vk_hash);
	let new_contract_address = CompleteAddress::compute(
	contract_dep_data.deployer_public_key,
	contract_dep_data.contract_address_salt,
	contract_dep_data.function_tree_root,
	constructor_hash,
	).address;