Added workflow to auto deploy master to test node

[lucacillario]

Greptile Summary

This PR adds a new GitHub Actions workflow file .github/workflows/deploy-testnet.yml that implements automatic deployment to testnet infrastructure. The workflow is designed to trigger whenever code is pushed to the master branch or when pull requests are merged into master.

The workflow uses a repository dispatch mechanism to communicate with the separate magicblock-labs/validator-deployment repository, which handles the actual deployment logic. This separation of concerns allows the validator codebase to trigger deployments while keeping deployment scripts and infrastructure configuration centralized in a dedicated repository.

Key components of the workflow include:

• Conditional execution logic that ensures it only runs on pushes to master or merged PRs
• Authentication using a GitHub personal access token (GH_PERSONAL_ACCESS_TOKEN)
• Comprehensive metadata payload including project name, target environment, branch information, triggering user, source repository, and commit SHA
• Integration with the existing CI/CD infrastructure by following similar patterns to the existing unit and integration test workflows

This change fits into the broader magicblock-validator ecosystem by providing automated continuous deployment capabilities that complement the existing CI workflows for unit and integration testing. It ensures that the testnet environment stays synchronized with the latest master branch changes without requiring manual intervention.

Confidence score: 4/5

• This PR is generally safe to merge with minimal risk to production systems
• Score reflects the straightforward nature of adding a deployment trigger workflow with proper conditionals and authentication
• Pay close attention to the GitHub token permissions and ensure the target repository is configured to handle the dispatch events

[greptile-apps]

_{1 file reviewed, 1 comment}

_{Edit Code Review Bot Settings | Greptile}

[GabrielePicco]

LGTM, but we should consider whether the workflow peter-evans/repository-dispatch@v3 should be internalized, since it’s a potential attack vector: it could be changed and DEPLOY_TRIGGER_TOKEN leaked.

[GabrielePicco]

LGTM!