feat(sr): Update ESP-SR to 2.x and enable it for ESP32-P4

[me-no-dev]

This pull request updates the ESP Speech Recognition (ESP_SR) component to support the ESP32P4 target and upgrades the underlying esp-sr dependency version. The main changes ensure that speech recognition features are now available for both ESP32S3 and ESP32P4 platforms when WakeNet or MultiNet are enabled.

Platform and Dependency Updates:

• Updated the espressif/esp-sr dependency version from ^1.4.2 to ^2.1.5 in idf_component.yml, and expanded its rules to include the ESP32P4 target.

Platform Support Expansion:

• Modified preprocessor conditionals in ESP_SR.cpp, ESP_SR.h, esp32-hal-sr.c, and esp32-hal-sr.h to include both CONFIG_IDF_TARGET_ESP32S3 and CONFIG_IDF_TARGET_ESP32P4, enabling speech recognition features for ESP32P4. [1] [2] [3] [4]

Fixes: #11783

[github-actions]

	Messages
📖	🎉 Good Job! All checks are passing!

👋 Hello me-no-dev, 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.

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 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.
4. If the change is approved and passes the tests it is merged into the default branch.

Generated by 🚫 dangerJS against 97b6f8e

[github-actions]

Memory usage test (comparing PR against master branch)

The table below shows the summary of memory usage change (decrease - increase) in bytes and percentage for each target.

Memory	FLASH [bytes]		FLASH [%]		RAM [bytes]		RAM [%]
Target	DEC	INC	DEC	INC	DEC	INC	DEC	INC
ESP32S3	0	0	0.00	0.00	0	0	0.00	0.00

Click to expand the detailed deltas report [usage change in BYTES]

Target	ESP32S3
Example	FLASH	RAM
libraries/ESP_SR/examples/Basic	-	-

[github-actions]

Test Results

 76 files   76 suites   13m 6s ⏱️
 38 tests  38 ✅ 0 💤 0 ❌
241 runs  241 ✅ 0 💤 0 ❌

Results for commit 97b6f8e.

♻️ This comment has been updated with latest results.