feat(ci): Build idf examples with overriden class driver components

[peter-marcisovsky]

Description

This MR runs IDF examples with all the components overriden.

Right now, only usb and esp_tinyusb Components are overriden in IDF examples, but class dirivers are still used from esp registry.

This would prevent us from breaking esp-idf CI before releasing any new component

Changes

Changes in the override_managed_component.py

• all components used in all esp-idf examples are now overridden and current versions of those components from esp-usb are used
• cherryUSB examples are excluded
• usb_host_lib as it does not contain any idf_component.yml is treated differently. First a idf_component.yml is created by the python script and then, the usb component is used as overridden.

Related

• Closes: IDF-14239 Build idf examples in CI with all components overridden

---

Checklist

Before submitting a Pull Request, please ensure the following:

• 🚨 This PR does not introduce breaking changes.
• All CI checks (GH Actions) pass.
• Documentation is updated as needed.
• Tests are updated or added as necessary.
• Code is well-commented, especially in complex areas.
• Git history is clean — commits are squashed to the minimum necessary.

---

Note

Enable overriding USB host class drivers in IDF examples CI, upgrade workflow tooling/flags, and enhance the override script with manifest handling and exclusions.

• CI Workflow (.github/workflows/build_idf_examples.yml):
  • Override USB host class drivers (host/class) for all releases; override core usb (host/usb) only on maintenance releases (v5.4, v5.5, latest).
  • Set EXAMPLES_PATH, upgrade idf-build-apps to 2.12.2, disable fail-fast, and export stricter compiler flags with Werror.
• Override Script (.github/ci/override_managed_component.py):
  • Add support to override esp_tinyusb, usb, and all class drivers; exclude CherryUSB examples.
  • Auto-create main/idf_component.yml for usb_host_lib when missing; improve app discovery and namespacing.
  • Special-case cdc_acm_vcp; add robust error handling, logging, and YAML IO.
• Build Config (.github/ci/.idf_build_examples_config.toml):
  • Add ignore_warning_files (use IDF's tools/ci/ignore_build_warnings.txt); remove work_dir.
• Build Rules (.github/ci/.idf-build-examples-rules.yml):
  • Tweak enable rules; add UVC gating for IDF_VERSION >= 5.5.

^{Written by Cursor Bugbot for commit aa22194. This will update automatically on new commits. Configure here.}

[peter-marcisovsky]

The same build error as from esp-idf here, CI Job failed correctly.

[peter-marcisovsky]

To be able to threat the sdkconfig warning as an CI Build error, this one which recently broke the esp-idf CI:

Loading defaults file /opt/esp/idf/examples/peripherals/usb/host/uvc/sdkconfig.defaults...
warning: unknown kconfig symbol 'PRINTF_UVC_CONFIGURATION_DESCRIPTOR' assigned to 'y' in /opt/esp/idf/examples/peripherals/usb/host/uvc/sdkconfig.defaults
Loading defaults file /opt/esp/idf/examples/peripherals/usb/host/uvc/sdkconfig.defaults.esp32p4...
warning: unknown kconfig symbol 'PRINTF_UVC_CONFIGURATION_DESCRIPTOR' assigned to 'y' in /opt/esp/idf/examples/peripherals/usb/host/uvc/sdkconfig.defaults.esp32p4

I updated the idf-build-apps to the current latest version. It, by default, contains a post-build action, which treats any warnings which occurred during build (and even before build) as a CI Build error. The same setup is present in esp-idf build CI.

Otherwise, without updating the idf-build-apps to the latest version, the build would have normally passed in our CI.

[tore-espressif]

@peter-marcisovsky Thank you for the work on this.

The original purpose of override_managed_component.py was to enable testing of examples or tests for components that are located outside their original repositories. The intent was for the script to remain reusable across different repositories facing similar constraints.

The proposed changes introduce behavior that is specific to the esp-usb repository. We should clarify whether we want to:

1. Redefine the scope of this script to be esp-usb-specific, or

2. Improve its design to keep it reusable.

If we choose the second option, possible improvements include:

• Invoking the script once for each overridden class driver, avoiding assumptions about component names derived from paths.

• Removing special-case handling for components that already contain an idf_component.yml file (e.g., usb_host_lib).