[docs-patrol] Update Dependency Review docs for trusted-users behavior

Recent code changes in the repository have introduced documentation drift. The following change needs a corresponding documentation update.

## Changes Requiring Documentation Updates

### 1. Dependency Review `allowed-bot-users` behavior changed but README semantics were not updated

**Commit(s):** [`b2ecc99`](https://github.com/elastic/ai-github-actions/commit/b2ecc99d30269f827b03ad9dc1ae9e4e26221b7f)

**What changed:**
- `.github/workflows/gh-aw-dependency-review.md` now configures:
- `github.min-integrity: approved`
- `github.trusted-users: ${{ inputs.allowed-bot-users }}`
- Evidence in current tree: `.github/workflows/gh-aw-dependency-review.md` lines 85-86.

**Documentation impact:**
- `gh-agent-workflows/dependency-review/README.md` still documents `allowed-bot-users` only as bot allowlisting for updatecli actors and does not explain the new GH-AW trusted-user integrity behavior.
- Evidence in current tree: `gh-agent-workflows/dependency-review/README.md` line 31.
- This is now inconsistent with other workflow READMEs that were updated in the same change set to include: “also GH-AW trusted-users under min-integrity approved”.

## Suggested Actions

- [ ] Update `gh-agent-workflows/dependency-review/README.md` input table row for `allowed-bot-users` to include its trusted-user integrity effect.
- [ ] Ensure the same wording is reflected anywhere Dependency Review input semantics are documented for users.

---
[What is this?](https://ela.st/github-ai-tools) | [From workflow: Trigger Docs Patrol](https://github.com/elastic/ai-github-actions/actions/runs/34487869192)

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.
> - [x] expires on Sep 17, 2026, 2:26 PM UTC

Read .github/workflows/gh-aw-dependency-review.md around lines 85-86 and compare it with the allowed-bot-users row in gh-agent-workflows/dependency-review/README.md around line 31. Update the README to describe both updatecli bot allowlisting and GH-AW trusted-user behavior under min-integrity approved, then check for other Dependency Review input documentation that needs the same wording.

Written by the indexing model from the issue text.