feat(matter): new matter example

[SuGlider]

Description of Change

This PR creates a new Matter example that demonstrates how to create a multi-endpoint node using a single event callback.

Tests scenarios

Testing the example with ESP32, S3, C3, C6.

Related links

#11535

[github-actions]

	Messages
📖	🎉 Good Job! All checks are passing!

👋 Hello SuGlider, 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.
- 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 db60c57

[github-actions]

Memory usage test (comparing PR against master branch)

The table below shows the summary of memory usage change (decrease - increase) in bytes and percentage for each target.

Memory	FLASH [bytes]		FLASH [%]		RAM [bytes]		RAM [%]
Target	DEC	INC	DEC	INC	DEC	INC	DEC	INC
ESP32S3	0	0	0.00	0.00	0	0	0.00	0.00
ESP32S2	0	0	0.00	0.00	0	0	0.00	0.00
ESP32C3	0	0	0.00	0.00	0	0	0.00	0.00
ESP32C6	0	0	0.00	0.00	0	0	0.00	0.00
ESP32	0	0	0.00	0.00	0	0	0.00	0.00

Click to expand the detailed deltas report [usage change in BYTES]

Target	ESP32S3		ESP32S2		ESP32C3		ESP32C6		ESP32
Example	FLASH	RAM	FLASH	RAM	FLASH	RAM	FLASH	RAM	FLASH	RAM
libraries/Matter/examples/MatterLambdaSingleCallbackManyEPs	-	-	-	-	-	-	-	-	-	-

[Copilot]

Pull Request Overview

This PR introduces a new Matter example demonstrating how to create a multi-endpoint node with a single event callback.

• Added new Matter keywords for endpoint identification and attribute operations.
• Provided CI configuration for the new example.
• Introduced an example sketch showcasing multi-endpoint on/off light control via a shared lambda callback.

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
libraries/Matter/keywords.txt	Added keywords for endpoint identification and attribute operations.
libraries/Matter/examples/MatterLambdaSingleCallbackManyEPs/ci.json	Defined CI settings for the new example.
libraries/Matter/examples/MatterLambdaSingleCallbackManyEPs/*.ino	New example sketch illustrating multi-endpoint callback usage.

Comments suppressed due to low confidence (1)

libraries/Matter/keywords.txt:119

• [nitpick] The keyword 'endpointIdentifyCB' has inconsistent casing compared to 'EndPointIdentifyCB'; consider aligning the casing to match existing conventions.

endpointIdentifyCB	KEYWORD2