Add Zigbee examples

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

Description of Change

This PR adds 2 examples to demonstrate usage of Zigbee stack:

• Zigbee_Light_Bulb -> Zigbee end device with LED.
• Zigbee_Light_Switch -> Zigbee Coordinator switching the LED on/off of the end device.

Supported SoCs are ESP32C6 and ESP32-H2.

Tests scenarios

Tested locally by flashing Zigbee_Light_Bulb to ESP32-C6 DevKitM and Zigbee_Light_Switch to ESP32-H2 DevKitM.
CI is skipping the examples for now, as we cannot specify the FQBN.

Related links

Closes #8807
Blocked by #9025 (new GPIO Interrupt enable/disable methods) -> Merged

[github-actions]

	Warnings
⚠️	Some issues found for the commit messages in this PR: the commit message "fix(example): Removed Serial and updated readme.": summary should not end with a period (full stop) Please fix these commit messages - here are some basic tips: follow Conventional Commits style correct format of commit message should be: <type/action>(<scope/component>): <summary>, for example fix(esp32): Fixed startup timeout issue allowed types are: change,ci,docs,feat,fix,refactor,remove,revert,test sufficiently descriptive message summary should be between 20 to 72 characters and start with upper case letter avoid Jira references in commit messages (unavailable/irrelevant for our customers) TIP: Install pre-commit hooks and run this check when committing (uses the Conventional Precommit Linter).
⚠️	Please consider squashing your 7 commits (simplifying branch history).
⚠️	The source branch "Zigbee-examples" incorrect format: contains uppercase letters. This can cause troubles on case-insensitive file systems (macOS). Please rename your branch.

👋 Hello P-R-O-C-H-Y, we appreciate your contribution to 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 8169a43

[SuGlider]

I have mixed feeling about it. It is an IDF code translated to compile in Arduino IDE.
I think that a broader work for creating comprehensive Arduino Classes would be more valuable.

This could be part of an example "in our own GH", but I'm sure this should be in the ESP32 Arduino repository.

[lucasssvaz]

I agree with @SuGlider. Just like the BLEMesh examples were added to gist, I think should be added there and linked in the docs until we have a proper lib.

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

@lucasssvaz @SuGlider Lets discuss it on todays meeting :)

[lucasssvaz]

As we discussed in the meeting, LGTM. Just need to fix the CI.

[VojtechBartoska]

Seems that we can close #8807 when this will be merged.

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

Added skip files for all SoCs to skip those examples in the Github CI, as we are not able now to specify FQNB separately for each example.

[me-no-dev]

why not run the main task in loop?

[me-no-dev]

or the button task?

[me-no-dev]

this task looks like something that you can just execute here.

[me-no-dev]

@P-R-O-C-H-Y ping

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

@me-no-dev Is it ok now?

• Removed the nvs_flash_init()
• In switch example, the button check now runs in loop
• I kept the Zigbee task for both examples, to keep the same approach. As in the switch example the loop runs the Button check.
• Fixed Zigbee ZCZR partition, in which I wrongly set an Offset.

[taiwansensortw]

I've seen examples of Zigbee devices like Zigbee_Light_Bulb and Zigbee_Light_Switch. Could you provide an example for a sensor, such as one for temperature and humidity? This would make the entire Zigbee architecture and usage clearer, allowing more people to get involved in this field.