[WIP] Expand .coderabbit.yml with WP-docs improvements and revalidate

[Copilot]

Thanks for asking me to work on this. I will get started on it and keep this PR's description up to date as I form a plan and make progress.

---

This section details on the original issue you should resolve

<issue_title>[Documentation] Expand .coderabbit.yml with WP-docs improvements and revalidate</issue_title>
<issue_description>Summary:
Expand the root .coderabbit.yml with improvements from the WP-docs repository and revalidate with the validation script.

Key Improvements Added:

• Added language: 'en-uk' and chat.auto_reply: true for explicit language and chat settings.
• Introduced status_checks and required_approvals for review workflow.
• Enhanced auto_labels with path-based rules for shell, docs, ci, test, js, python.
• Improved auto_assign reviewer logic.
• Expanded path_filters to exclude more build/cache/vendor/test artefacts.
• Added granular path_instructions for scripts, workflows, changelog, README, and markdown files, including automation and governance checks.
• Added detailed review instructions for shell, JS, Python scripts, workflows, changelog, README, and bats tests.

Validation Result:

• Ran validate-coderabbit-yml.cjs after changes: .coderabbit.yml is valid! (schema: local)
• Used local schema due to fetch error, but validation passed.

Differences from previous version:

• The previous .coderabbit.yml did not include language/chat, status_checks, required_approvals, or the expanded path_instructions for scripts, workflows, and markdown files.
• Path filters and auto_labels/auto_assign logic are now more comprehensive and granular.
• Review instructions are now more modular and cover more file types and automation scenarios.

Action:

• Review and maintain the expanded .coderabbit.yml for future improvements.
• Ensure schema fetch is fixed for remote validation in future.

---

Template: 19-documentation.md
Type: Documentation
Labels: documentation, automation, governance
Assignee: ashleyshaw</issue_description>

<agent_instructions>Proceed with issue </agent_instructions>

Comments on the Issue (you are @copilot in this section)