Support easy recovery for deploy and upgrade during network congestion

[abcoathup]

Ideally there would be support for easy recovery for deploy and upgrade during network congestion.

deploy requires 3 transactions, upgrade 2 transactions.
During network congestion, transactions can quickly be underpriced resulting in delays for transactions to be added to blocks resulting in timeouts.

Configuration either needs to be manually edited to add contract details once transactions are mined and then the process restarted to continue where it left off or the whole process retried.

Recent examples in the forum include:

• https://forum.openzeppelin.com/t/how-to-recover-from-a-timeout-due-to-network-congestion-when-deploying-an-upgradeable-contract-on-mainnet/3049
• https://forum.openzeppelin.com/t/deploy-hangs-on-deploying-to-mainnet/3524
• https://forum.openzeppelin.com/t/upgrading-on-mainnet-fails-but-transaction-fees-are-taken/3575

[frangio]

This situation is better supported by the OpenZeppelin Upgrades plugins since deployments are stored in the file system even if the transaction times out, and a subsequent run of the plugin will resume waiting until the transaction mines rather than sending it again.