Update Bits Code PR/MR collaboration providers

[cketcham]

What does this PR do? What is the motivation?

Bits Code supports @Datadog mentions in GitLab merge request and Azure DevOps pull request comments, and it maintains a status comment on the pull or merge request while it works on a request. The docs still described mentions as GitHub-only, listed GitLab as an explicit limitation, and didn't cover the Azure DevOps permission that the status comment's CI Auto-fix action depends on.

Source PR: https://github.com/DataDog/code-gen-backend/pull/15137

Changes

• The pull or merge request collaboration section covers @Datadog mentions on GitHub, GitLab, and Azure DevOps, and describes what customers see in the status comment: the run state, the actions and links available to them, a link to the Datadog session, and CI Auto-fix status and controls when available.
• The obsolete GitLab limitation is gone, so the page no longer contradicts itself about provider support.
• The Azure DevOps setup tab asks customers to let the integration service principal view builds, and states the fallback: if the permission is missing, the status comment prompts for it instead of offering an action that can't succeed.

Both edits stay in the shape of what they touch — a reworded bullet and a short paragraph in an existing prose section, and one numbered step alongside the other Azure DevOps setup requirements. No renderer, event, or permission-check internals are described.

Testing

• Verified the Markdown structure of the new Azure DevOps step: it continues the tab's existing numbered list, and the new [105] reference link is defined inside the same tab block as that tab's other reference links.
• Grepped the overview page for leftover GitHub-only claims about mentions; the only remaining provider-specific wording is the supported-providers list, which is unchanged and already lists all three providers.
• Vale was not run: the binary and its ../datadog-vale styles are not available in this environment. The new copy was checked by hand against the substitution list in CLAUDE.md (no "ensure", "via", "just", "currently/now", or filler words).
• The new Microsoft Learn link for build permissions could not be opened from this environment (external fetches are blocked), so it's worth one click during review.

Merge readiness

• Ready for merge

For Datadog employees:

• ⚠️ Your branch name MUST follow the <name>/<description> convention and include the forward slash (/). If you've already created your PR with an incorrect branch name, please rename your branch and open a fresh PR.
• 🤖 New: Comment with /review to run an automated check that catches common issues before a Documentation team member reviews your PR.

AI assistance

Drafted with Bits Code (Claude Code); wording reviewed manually against the repo style guide.

Additional notes

No Jira ticket was provided for this change, so the title omits a DOCS- key.

---

PR by Bits - View session in Datadog

Comment @DataDog to request changes

[datadog-datadog-us1-prod]

View session in Datadog

Bits Code status: ✅ Done

Comment @DataDog to request changes

[datadog-datadog-prod-us1-2]

I can only run on private repositories.

[github-actions]

Preview links (active after the build_preview check completes)

Modified Files

• https://docs-staging.datadoghq.com/dd/cameron.ketcham/bits-code-pr-mr-collaboration-providers/bits_ai/bits_code/
• https://docs-staging.datadoghq.com/dd/cameron.ketcham/bits-code-pr-mr-collaboration-providers/bits_ai/bits_code/setup