feat(zigbee): Update to esp-zigbee-sdk 1.6.5 and fix ci.json files

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

Description of Change

This pull request includes updates to Zigbee-related dependencies and configuration files to ensure compatibility with newer library versions and streamline build requirements.

Dependency Updates:

• idf_component.yml: Updated espressif/esp-zboss-lib to version 1.6.4 for compatibility with esp-zigbee-lib version 1.6.5. Updated espressif/esp-zigbee-lib to version 1.6.5. These changes ensure compatibility between Zigbee libraries.

Tests scenarios

Tested Zigbee compilation on ESP32-C6 and tested Analog example on ESP32-C5, that successfully connects to HA Zigbee network.

Related links

[github-actions]

	Warnings
⚠️	The **target branch** for this Pull Request **must be the default branch** of the project (`master`). If you would like to add this feature to a different branch, please state this in the PR description and we will consider it.

👋 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.
- Resolve all warnings (⚠️ ) before requesting a review from human reviewers - they will appreciate it.
- 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 45e953b