[openthread] Docs for static log level code quality improvement

[rwrozelle]

Description

Documentation for changes to the internal logging of the openthread task from dynamic to static using CONFIG_OPENTHREAD_LOG_LEVEL_ setting.
The OpenThread log level is now controlled by the esp32.framework.log_level setting. The ESP-IDF log level labels are mapped to OpenThread log levels:

0 NONE -> NONE
1 ERROR -> CRIT
2 WARN -> WARN
3 INFO -> NOTE
4 DEBUG -> INFO
5 VERBOSE -> DEBG
This is a breaking change because the OpenThread log level was previously dynamic and is now statically set based on the framework log level.
Related issue (if applicable): fixes

Pull request in esphome with YAML changes (if applicable):

• [openthread] static log level code quality improvement esphome#14456

Checklist

• I am merging into next because this is new documentation that has a matching pull-request in esphome as linked above.
  or

• I am merging into current because this is a fix, change and/or adjustment in the current documentation and is not for a new component or feature.

• Link added in /src/content/docs/components/index.mdx when creating new documents for new components or cookbook.

New Component Images

If you are adding a new component to ESPHome, you can automatically generate a standardized black and white component name image for the documentation.

To generate a component image:

1. Comment on this pull request with the following command, replacing component_name with your component name in lower_case format with underscores (e.g., bme280, sht3x, dallas_temp):

   @esphomebot generate image component_name
   

2. The ESPHome bot will respond with a downloadable ZIP file containing the SVG image.

3. Extract the SVG file and place it in the /public/images/ folder of this repository.

4. Use the image in your component's index table entry in /src/content/docs/components/index.mdx.

Example: For a component called "DHT22 Temperature Sensor", use:

@esphomebot generate image dht22

Note: All images used in ImgTable components must be placed in /public/images/ as the component resolves them to absolute paths.

[netlify]

✅ Deploy Preview for esphome ready!

Name	Link
🔨 Latest commit	2a22214
🔍 Latest deploy log	https://app.netlify.com/projects/esphome/deploys/69aeb438d8689000081f918f
😎 Deploy Preview	https://deploy-preview-6219--esphome.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[swoboda1337]

Thanks