fix(reviewer-bot): clarify /release command behavior and guidance

[PLeVasseur]

Summary

• make /release usage explicit everywhere the bot documents commands by splitting self release and triage release forms
• improve /release failure messaging for non current reviewers with actionable guidance that points to /release @current-reviewer
• add regression tests for guidance text, /commands output, and the confusing non current reviewer release paths

Testing

• uv run ruff check --fix scripts/reviewer_bot.py .github/reviewer-bot-tests/test_reviewer_bot.py
• uv run python -m pytest .github/reviewer-bot-tests/test_reviewer_bot.py -k release
• uv run python -m pytest .github/reviewer-bot-tests/test_reviewer_bot.py

Closes #406

[netlify]

✅ Deploy Preview for scrc-coding-guidelines ready!

Name	Link
🔨 Latest commit	8ec4b51
🔍 Latest deploy log	https://app.netlify.com/projects/scrc-coding-guidelines/deploys/6995e38008584d0008be83ff
😎 Deploy Preview	https://deploy-preview-410--scrc-coding-guidelines.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[felix91gr]

@PLeVasseur should it be /release @<current_reviewer_s_username> <reason>?

From the context of where the command is invoked, it would always know who the current reviewer is, right?

[sei-dsvoboda]

@guidelines-bot /r? producers

[github-actions]

@cpetig is designated as reviewer by queue rotation, but GitHub could not add them to PR Reviewers automatically (API 422). A triage+ approver may still be required before merge queue.

[github-actions]

✅ @cpetig remains designated as reviewer in bot state. GitHub reviewer assignment could not be completed.

[plaindocs]

@PLeVasseur do we need to get this merged in?

[PLeVasseur]

@PLeVasseur do we need to get this merged in?

Yeah, that'd probably be wise.

I need to reorient myself. Next week looks more open for me to do that.