fix(openthread): fix RCP build to pass time sync and CSL options (IDFGH-13113)

[no2chem]

This PR fixes an issue where the menuconfig option OPENTHREAD_TIME_SYNC is set but OPENTHREAD_CONFIG_TIME_SYNC_ENABLE is never defined during a RCP build, resulting in an RCP build without time sync enabled. The same bug applies for CSL.

Fixes #14059

[CLAassistant]

All committers have signed the CLA.

[github-actions]

	Messages
📖	🎉 Good Job! All checks are passing!

👋 Hello no2chem, 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 via this public GitHub repository.

This GitHub project is public mirror of our internal git repository

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 synchronize it into our internal git repository.
4. In the internal git repository 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.
5. If the change is approved and passes the tests it is merged into the default branch.
5. On next sync from the internal git repository merged change will appear in this public GitHub repository.

Generated by 🚫 dangerJS against 93d9982

[chshu]

@no2chem Thank you for your contribution!

It's indeed a feature has not been supported in current SDK. CSL was introduced in Thread 1.2, but it has not yet seen widespread adoption in products. Time Sync is still an experimental feature and is not defined in the Thread specification.

Both the features are well supported by single SoC, and we will evaluate the feasibility of supporting them in RCP mode. Could you provide more details about your product use case? Is it based on ESP Thread BR?

[no2chem]

Thanks @chshu -

We would like to use it with ESP thread BR - but the library is not open source so we are using ot-br-posix instead.

We've run into some stability issues with ESP thread BR so we're not as confident in using it because we can't fix it, but since the RCP should be agnostic to whether ESP thread BR or ot-br-posix is running on the NCP.

But both features work in RCP mode once the changes in this PR are applied, and #14089 is used to fix a bug in the 802154 state machine.

[chshu]

@no2chem The change looks good with 2 minor comments, we will do some verification internally, and merge it then.

For any stability issue you encountered, please test again with the latest release/v5.1 branch, and feel free to file issues here: https://github.com/espressif/esp-thread-br.

[chshu]

It's duplicate with previous line.

[chshu]

It's a new definition in OpenThread upsteam repo, but the OT submodule in IDF doesn't have the change yet. Could you please revert this change, and make sure it works with the current OT verion in IDF.

We will update the OT submodule in July.