docs(red-teaming): fix gpt-5.4 typo and complete exports list

[Aryansharma28]

Summary

• Replace placeholder model id openai/gpt-5.4 with openai/gpt-4o across all red-teaming docs (main page, quick-start, GOAT). It was a copy-paste typo — the rest of the docs site uses gpt-4o/gpt-4o-mini, and any reader running the snippets verbatim would have hit a model-not-found error.
• Expand the Python Exports section on the main red-teaming page to include GoatStrategy, AttackTechnique, and Technique, all of which are publicly exported from scenario (verified in python/scenario/__init__.py) but were previously absent from the docs.

Test plan

• cd docs && pnpm dev (or equivalent) and visually verify the three pages render correctly
• Spot-check that the Python snippets in red-teaming.mdx, red-teaming/quick-start.mdx, and red-teaming/goat.mdx are copy-pasteable and reference real models
• Confirm the new Exports lines (GoatStrategy, AttackTechnique, Technique) actually import: python -c "from scenario import GoatStrategy, AttackTechnique, Technique"

🤖 Generated with Claude Code

[github-actions]

Automated low-risk assessment

This PR was evaluated against the repository's Low-Risk Pull Requests procedure.

• Scope: Update red‑teaming docs (red-teaming.mdx, goat.mdx, quick-start.mdx) to use openai/gpt-4o instead of openai/gpt-5.4 and add GoatStrategy, AttackTechnique, and Technique to the Python Exports section.
• Exclusions confirmed: no changes to auth, security settings, database schema, business-critical logic, or external integrations.
• Classification: low-risk-change under the documented policy.

The changes are limited to documentation: replacing a placeholder model id (openai/gpt-5.4 → openai/gpt-4o) in red‑teaming docs and expanding the Python Exports list to include GoatStrategy, AttackTechnique, and Technique. No authentication, secrets, database schemas, business‑critical logic, or external integrations are modified, so the PR meets the low‑risk criteria.

This classification allows merging without manual review once all required CI checks are passing and branch protection rules are satisfied.