[Request] Add support for Wake-up Coordinator and Wake-up End Device

Add support for Wake-up Coordinator and Wake-up End Device

Context

OpenThread recently added two new complementary Thread roles for even lower power consumption than a standard Sleepy End Device (SED):

• Wake-up Coordinator - a device (typically the Border Router or a router) that can "wake up" another device by sending it a sequence of wake-up frames.
• Wake-up End Device (WED) - an ultra-low-power device that stays essentially dormant and only briefly listens on the network at regular intervals to detect an incoming wake-up frame.

Unlike a classic SED, which regularly polls its parent router to check for pending messages (consuming energy even when there's nothing to receive), a WED almost never activates on its own - the network wakes it up on demand instead.

Code

Wakeup channel parameter added here:
[otci] add the parameter wakeup channel to the method create_dataset #10898

Doc

https://openthread.io/reference/config/group/config-wakeup

December 6, 2024

• Added new wakeup wake command to the CLI Command Reference.
• Added new otThreadWakeup function to the General API.
• Added the OPENTHREAD_CONFIG_WAKEUP_COORDINATOR_CONNECTION_RETRY_COUNT and OPENTHREAD_CONFIG_WAKEUP_COORDINATOR_CONNECTION_RETRY_INTERVAL macros to the Wake-up module of the Configuration Variables Reference.

No repository files, tests, or entry points are identified in the issue. Start by reviewing the linked OpenThread wake-up configuration and API documentation, then inspect the existing python-otbr-api surface for related Thread device or dataset support. Done should cover the requested Wake-up Coordinator and Wake-up End Device support, including the listed wake-up channel, CLI/API, and configuration details.