feat(docs): Add Zigbee library API documentation

[P-R-O-C-H-Y]

Description of Change

This pull request adds documentation for new Zigbee library, expanding the API coverage.

• Added Zigbee APIs to Table of Contents: Included a new section in libraries.rst that organizes Zigbee-related APIs under their own subsection, improving navigation and discoverability.

Tests scenarios

Related links

Closes #10135

[github-actions]

	Messages
📖	This PR seems to be quite large (total lines of code: 4186), you might consider splitting it into smaller PRs

👋 Hello P-R-O-C-H-Y, we appreciate your contribution to this project!

---

📘 Please review the project's Contributions Guide for key guidelines on code, documentation, testing, and more.

---

🖊️ Please also make sure you have read and signed the Contributor License Agreement for this project.

---

Click to see more instructions ...

This automated output is generated by the PR linter DangerJS, which checks if your Pull Request meets the project's requirements and helps you fix potential issues.

DangerJS is triggered with each push event to a Pull Request and modify the contents of this comment.

Please consider the following:
- Danger mainly focuses on the PR structure and formatting and can't understand the meaning behind your code or changes.
- Danger is not a substitute for human code reviews; it's still important to request a code review from your colleagues.
- Addressing info messages (📖) is strongly recommended; they're less critical but valuable.
- To manually retry these Danger checks, please navigate to the Actions tab and re-run last Danger workflow.

Review and merge process you can expect ...

We do welcome contributions in the form of bug reports, feature requests and pull requests.

1. An internal issue has been created for the PR, we assign it to the relevant engineer.
2. They review the PR and either approve it or ask you for changes or clarifications.
3. Once the GitHub PR is approved we do the final review, collect approvals from core owners and make sure all the automated tests are passing.
- At this point we may do some adjustments to the proposed change, or extend it by adding tests or documentation.
4. If the change is approved and passes the tests it is merged into the default branch.

Generated by 🚫 dangerJS against c00305c

[pedrominatel]

Thank you very much for your contribution, @P-R-O-C-H-Y. It will take some time, but I'll review ASAP.

[lucasssvaz]

I think there are some leftover python and temp files

[Copilot]

Pull Request Overview

This PR introduces comprehensive API documentation for the new Zigbee library and supporting scripts to clean up and standardize existing RST files.

• Added scripts to remove example blocks and fix RST underlines
• Expanded libraries.rst with a new Zigbee section in the table of contents
• Created detailed API reference files under docs/en/zigbee/ for core and endpoint classes

Reviewed Changes

Copilot reviewed 31 out of 32 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
remove_api_examples.py	Script to strip individual API examples from RST files
fix_rst_underlines.py	Script to correct RST subtitle underlines
docs/fix_rst_underlines.py	Duplicate underline-fixing script in docs/ directory
docs/en/libraries.rst	Added Zigbee APIs section to library index
docs/en/zigbee/zigbee.rst	Top-level Zigbee overview and toctree
docs/en/zigbee/zigbee_core.rst	Core class (ZigbeeCore) API documentation
docs/en/zigbee/zigbee_ep.rst	Base endpoint (ZigbeeEP) API documentation
docs/en/zigbee/ep_*.rst	Individual endpoint API reference files

Comments suppressed due to low confidence (3)

docs/en/zigbee/zigbee.rst:70

• The text refers to a Zigbee class, but elsewhere the core class is named ZigbeeCore. For consistency, update this reference to ZigbeeCore or clarify the naming.

The Zigbee class is implemented as a singleton, meaning there's only one instance available globally. You access it directly as ``Zigbee`` without creating an instance.

fix_rst_underlines.py:1

• [nitpick] There are two fix_rst_underlines.py scripts in separate directories. It would improve maintainability to consolidate them into a single, well-documented script.

#!/usr/bin/env python3

remove_api_examples.py:13

• [nitpick] The regex for matching example blocks may not cover all code-block variations and could miss multi-sentence sections. Consider using a more robust pattern (e.g., matching until a blank line or next heading) to ensure complete removal.

    pattern = r'\*\*Example:\*\*\s*\n\s*\n\s*\.\. code-block:: arduino\s*\n\s*\n\s*[^.]*?\.\s*\n\s*\n'

[P-R-O-C-H-Y]

I think there are some leftover python and temp files

@lucasssvaz Removed, thanks :)