chore(ci): add Update Test workflow for bulk test snapshot updates

[devin-ai-integration]

Description

Refs https://app.devin.ai/sessions/f14c47d1bcb14fe18b15d5b93f0147a2

Requested by: judah@buildwithfern.com (@jsklan)

Adds a new manually-triggered GitHub Actions workflow called "Update Test" that runs pnpm test:update and pnpm test:ete:update to bulk update test snapshots remotely, similar to the existing "Update Seed" workflow. The workflow commits and pushes changes directly to the branch it runs on.

Changes Made

• Added .github/workflows/update-test.yml workflow file
• Workflow is triggered manually via workflow_dispatch only
• Restricted to non-main branches with condition github.ref != 'refs/heads/main'
• Runs both pnpm test:update and pnpm test:ete:update commands
• Commits and pushes changes directly using EndBug/add-and-commit@v9 (following the commit-seed-changes-by-push pattern from update-seed.yml)
• Includes setup steps for buf, Go, and protoc-gen-openapi (copied from CI test jobs)

Testing

⚠️ This workflow has not been manually triggered yet.

• Verified pnpm test:update and pnpm test:ete:update scripts exist in package.json
• Verified workflow follows the commit-seed-changes-by-push pattern from update-seed.yml
• Manual trigger needed: Workflow should be tested on a non-main branch to verify end-to-end functionality

Human Review Checklist

• Test the workflow: Manually trigger on a test branch to verify it works end-to-end
• Review file staging pattern: Currently uses add: "." which stages all changes. Should this be more specific (e.g., only test snapshot files)?
• Verify setup dependencies: Are buf, Go, and protoc-gen-openapi actually needed for these test commands, or can some setup steps be removed?
• Confirm secrets: Verify FERN_ORG_TOKEN_DEV secret is configured in the repository
• Branch restriction: Confirm the github.ref != 'refs/heads/main' condition correctly prevents running on main branch

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring