chore: update tend workflows (0.1.13 → 0.1.14)

[prql-bot]

Nightly regeneration of tend's workflow files via uvx tend@latest init.

tend version: 0.1.13 → 0.1.14

Notable changes

• Jobs now declare environment: {name: tend, deployment: false} instead of the bare environment: tend (workflows: name the environment with deployment: false max-sixty/tend#852, check: refuse a job that names the environment and files a deployment max-sixty/tend#853). GitHub was filing a deployment record for every tend run and posting it on the pull request; this stops that. It also clears the environment-deployments failure currently tracked in tend check: configuration drift on PRQL/prql #6127.
• tend-mention's engagement check no longer counts bot comments/reviews inside jq (fix(mention): count bot engagement outside jq so --paginate can't split it max-sixty/tend#840). gh api --paginate applies --jq once per page, so | length emitted one count per page — past 100 comments the shell test errored and fell through to should_run=false, silencing the bot on its most-engaged threads.
• tend check now sweeps credential-holding environments rather than only secret-holding ones (check: sweep credential-holding environments, not just secret-holding ones max-sixty/tend#815). This is why tend check: configuration drift on PRQL/prql #6127's secret-environments entry became credential-environments and picked up the github-pages and OIDC-job findings.
• /code-review is now a tend-owned skill rather than a borrowed one (fix(review): port /code-review into a tend-owned skill max-sixty/tend#819), and the review-record guards ignore synthetic reply containers (fix(review): ignore synthetic reply containers in all three review-record guards max-sixty/tend#835).
• Assorted fixes to triage PR-body templating (fix(triage): substitute the issue number into the PR-body templates max-sixty/tend#844), stranded outage-row attribution (fix(report-failure): name the trigger a stranded outage row points at max-sixty/tend#823), and transient run-metadata fetch failures when marking notifications read (fix(mark-notification-read): tolerate a transient run-metadata fetch failure max-sixty/tend#843).

The id-token: write permission is also dropped from the tend jobs, since nothing in the harness mints an OIDC token.

Full upstream diff: max-sixty/tend@0.1.13...0.1.14