Use GitHub token for TagBot releases

[quinnj]

Summary

• use the repository GITHUB_TOKEN for TagBot tag pushes
• avoid selecting the stale SSH deploy key path

Root cause

TagBot changes its Git remote to SSH whenever the ssh input is non-empty. The configured DOCUMENTER_KEY no longer authenticates to this repository, while the workflow already grants contents: write to GITHUB_TOKEN.

Validation

• the workflow YAML parses
• git diff --check passes
• the final master documentation deploy proved the token permission path works

Co-authored by Codex

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.25%. Comparing base (450599b) to head (21c93be).

Additional details and impacted files

@@           Coverage Diff           @@
##           master      #58   +/-   ##
=======================================
  Coverage   82.25%   82.25%           
=======================================
  Files           1        1           
  Lines         124      124           
=======================================
  Hits          102      102           
  Misses         22       22           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.