feat(board): Add support for DFRobot FireBeetle 2 ESP32-P4

[me-no-dev]

This pull request introduces support for the DFRobot FireBeetle 2 ESP32-P4 board by adding its configuration to the Arduino build system and defining its pin mappings. The most important changes are grouped below:

Board configuration and build settings:

• Added configuration entries for the dfrobot_firebeetle2_esp32p4 board in boards.txt, including upload tools, build settings, partition schemes, JTAG adapter options, upload speeds, debug levels, and flash erase options. This enables the board to be selected and built in the Arduino IDE.

Pin mapping and hardware definitions:

• Created the pins_arduino.h file for the dfrobot_firebeetle2_esp32p4 variant, defining all key pin mappings (digital, analog, SPI, I2C, I2S, SDMMC, and WiFi/SDIO), as well as board-specific macros for features like SDMMC and WiFi. This ensures compatibility with Arduino sketches and libraries.

Product Wiki: https://wiki.dfrobot.com/SKU_DFR1172_FireBeetle_2_Board_ESP32_P4

[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 ec161f6