Hardhat Ignition 1.0.0

[alcuadrado]

I'm creating this issue to inform users about our top priorities for the first stable version of Hardhat Ignition.

TypeChain support (#156)

Hardhat Ignition should work seamlessly with TypeChain. Currently, if you call ignition.deploy() from one of your tests, it returns objects of type ethers.Contract, instead of taking advantage of TypeChain. This will be fixed soon.

create2 support (#91)

Users should be able to deploy their modules using a create2 factory, without modifying the modules themselves. Using or not create2 should be a config field or command line parameter.

Better ABI validation (#278)

We should validate that every call and deployment receives arguments of the right type. Ideally, this validation should be done at runtime and by the type system.

Viem support (#589)

The current version of Hardhat Ignition only supports ethers v6. We should also support Viem.

End-to-end integration with Wagmi (#202)

We should have a clear story about how Hardhat Ignition should be used with Wagmi, where things work seamlessly, without having to copy artifacts and addresses around.

Lighter deployment artifacts (#599)

We should make our deployment artifacts lighter and friendlier for version control.

There are two things obvious paths forward here:

1. Make the BuildInfo files lighter. This can be done by not saving their output information.
2. Journal pruning: We should consider "compressing" the journal by pruning it after successful runs. For example, if a deployment future is executed successfully, we can replace all of its messages with a single one.