Introduce github action to run CI on new snarkVM revs

[iamalwaysuncomfortable]

Motivation

Note: originally created by @vicsn but merged into a branch on this repo to enable it to run properly.

Similar to: ProvableHQ/snarkOS#3814

Introduces a github action to allow automated testing on snarkVM updates:

• Pushes to a update-snarkvm-staging branch if a new snarkVM staging branch rev was found
• Opens a PR if it wasn't opened yet

Test Plan

You can try it out by pushing this as a branch to ProvableHQ/SDK:ci/snarkvm-update

I don't have write permissions to the SDK repo so I can't push there or add reviewers, so doing a manual tag: @iamalwaysuncomfortable

[Copilot]

Pull Request Overview

This PR introduces a GitHub Actions workflow to automatically update snarkVM dependencies when new commits are available on the staging branch. The workflow runs hourly to check for updates and creates pull requests when changes are detected.

• Automated hourly checks for new snarkVM staging commits
• Updates multiple snarkVM dependencies in the wasm directory using cargo commands
• Creates pull requests automatically when updates are found

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

The commit message references current_commit on line 90, but this output variable is never set in the snarkvm-commit step. Only latest_commit is defined on line 42. This will result in an empty value being displayed in the commit message.

[Copilot]

The PR body references current_commit which is not defined in the snarkvm-commit step outputs. This will result in an empty value being displayed in the pull request description.

[Copilot]

The summary step references current_commit output which doesn't exist. Only latest_commit and update_needed are set as outputs in the snarkvm-commit step.

Suggested change

echo "- Current snarkVM commit: ${{ steps.snarkvm-commit.outputs.current_commit }}" >> $GITHUB_STEP_SUMMARY

[Copilot]

The update_needed output is hardcoded to 'true', which means the workflow will always attempt to update regardless of whether there are actual changes. Consider implementing logic to compare the current commit with the latest commit to determine if an update is actually needed.

Suggested change

	core.setOutput('latest_commit', latestCommit);
	core.setOutput('update_needed', 'true');
	// Read the currently used snarkVM commit hash from Cargo.lock
	const fs = require('fs');
	let currentCommit = null;
	try {
	const lockFile = fs.readFileSync('Cargo.lock', 'utf8');
	const match = lockFile.match(/name = "snarkVM"[^\n]*\n(?:[^\n]*\n)*?source = "git\+https:\/\/github\.com\/ProvableHQ\/snarkVM\.git\?rev=([a-f0-9]+)"/);
	if (match && match[1]) {
	currentCommit = match[1];
	}
	} catch (e) {
	console.log('Could not read current snarkVM commit from Cargo.lock:', e);
	}
	console.log('Current snarkVM commit in Cargo.lock:', currentCommit);
	core.setOutput('latest_commit', latestCommit);
	if (currentCommit && currentCommit === latestCommit) {
	core.setOutput('update_needed', 'false');
	} else {
	core.setOutput('update_needed', 'true');
	}

[iamalwaysuncomfortable]

@vicsn we'll test this out over the next few days.