chore: move the website to the new staging cluster/account

[levivannoort]

What does this PR do?

Changes the cluster the website runs on by changing the token used to the new account.

Test Plan

N/A

Related PRs and Issues

N/A

Have you read the Contributing Guidelines on issues?

N/A

Summary by CodeRabbit

• Chores
  • Updated staging environment deployment configuration to use separate API credentials.

[coderabbitai]

Walkthrough

The staging deployment workflow configuration was updated to use a different DigitalOcean API token secret. The Doctl step now references STG_DIGITALOCEAN_ACCESS_TOKEN instead of DIGITALOCEAN_ACCESS_TOKEN. This is a single-line substitution with no changes to workflow logic, error handling, or control flow.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: updating the DigitalOcean API token secret reference in the staging deployment workflow to use the new staging cluster/account credentials.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

• 📝 Generate docstrings (stacked PR)
• 📝 Generate docstrings (commit on current branch)

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch CLO-3895

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}