Implement retry/resume functionality for [create] & [setup] steps

[anuragchvn-blip]

PR Description for Issue #71 Implementation

Title: Implement retry/resume functionality for [[create]] & [[setup]] steps

Description:

This PR implements the retry and resume functionality for both [[create]] and [[setup]] steps as requested in issue #71.

Changes Made:

1. Create Steps Resume:

   • Added logic to check existing entries in the named_txs table before deploying contracts
   • Contracts that already exist in the database are skipped during subsequent runs
   • Proper counting mechanism to track multiple deployments with the same name

2. Setup Steps Resume:

   • Created setup_progress table with scenario_hash and last_step_index fields
   • Added get_setup_progress and update_setup_progress database methods
   • Implemented step indexing to track completed setup transactions
   • Resume execution from the last completed step

3. Database Schema:

   • Added setup_progress table: (scenario_hash TEXT PRIMARY KEY, last_step_index INTEGER NOT NULL)
   • ON CONFLICT handling for progress updates

4. Error Handling:

   • Proper failure handling that preserves progress when setup steps revert
   • Execution stops on failure while maintaining completed steps

Technical Details:

• Create steps use name-based lookup in named_txs to determine which deployments to skip
• Setup steps use scenario hash-based progress tracking with step indexing
• Both implementations handle the redeploy flag properly
• Progress is preserved in the database for resumable execution

Testing:

• Database-level tests validate the setup_progress functionality
• Integration tests verify the resume behavior works correctly
• Existing functionality remains unchanged

This resolves issue #71 by allowing users to resume failed scenario deployments without losing progress.