Ignition: fix for bug when we fail to save transaction hash

[zoeyTM]

In this PR

• added new journal message TRANSACTION_PREPARE_SEND that is written to journal immediately before sending a transaction to the network
• added new logic to execution engine that checks the deployment state for any execution state that has a nonce but no transactions and throws if it finds one, alerting the user and asking them to find the appropriate transaction on a block explorer and use the new track-tx command to add it to the deployment
• added a new track-tx command that allows users to add a missing transaction back to their deployment. accounts for several edge cases
• tests for all of the above

[changeset-bot]

🦋 Changeset detected

Latest commit: 84a763e

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 5 packages

Name	Type
@nomicfoundation/ignition-core	Patch
@nomicfoundation/ignition-ui	Patch
@nomicfoundation/hardhat-ignition	Patch
@nomicfoundation/hardhat-ignition-ethers	Patch
@nomicfoundation/hardhat-ignition-viem	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
hardhat	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 12, 2025 7:55am

[alcuadrado]

I'm not sure if I understand this part, let's look at it on a call. Other than that LGTM.

[alcuadrado]

self-answer: This works because it's the else to the if in line 104. Hence, the transaction matches the sender and nonce, but not data and value. i.e. a replacement.

[alcuadrado]

Re-reviewed this, and now I get it. I think the else in the newline was confusing me.