Main work

[Jason2866]

No description provided.

[github-actions]

	Warnings
⚠️	The PR description looks very brief, please check if more details can be added.
⚠️	Some issues found for the commit messages in this MR: the commit message Update bt lib for ESP32-C3 and ESP32-S3(c8aa206) appears to be a temporary or automatically generated message the commit message change(wpa_supplicant): clean up test_dpp, set leak threshold appears to be a temporary or automatically generated message the commit message change(wpa_supplicant): clean up test_eloop, set leak threshold appears to be a temporary or automatically generated message the commit message change(wpa_supplicant): clean up test_sae, set leak thresholds appears to be a temporary or automatically generated message the commit message change(wpa_supplicant): test_offchannel: cleanups and leak thresholds appears to be a temporary or automatically generated message the commit message ci(system): re-enable build test app for C2 and C6, clean up configs appears to be a temporary or automatically generated message Please consider updating these commit messages.

	Messages
📖	You might consider squashing your 223 commits (simplifying branch history).

---

👋 Welcome Jason2866, thank you for your first contribution to espressif/esp-idf project!

📘 Please check Contributions Guide for the contribution checklist, information regarding code and documentation style, testing and other topics.

🖊️ Please also make sure you have read and signed the Contributor License Agreement for espressif/esp-idf project.

Pull request review and merge process you can expect

Espressif develops the ESP-IDF project in an internal repository (Gitlab). We do welcome contributions in the form of bug reports, feature requests and pull requests via this public GitHub 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 master branch
6. On next sync from the internal git repository merged change will appear in this public Github repository

---

_{🔁 You can re-run automatic PR checks by retrying the DangerJS action}

Generated by 🚫 dangerJS against 6cbc323