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

[tangjie133]

This pull request introduces support for the DFRobot FireBeetle 2 ESP32-C5 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_esp32c5 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_esp32c5 variant, defining all key pin mappings (digital, analog, SPI, I2C, , and GDI). This ensures compatibility with Arduino sketches and libraries.
Product Wiki: https://wiki.dfrobot.com/SKU_DFR1222_Firebeetle_2_ESP32_C5_Development_Board

[CLAassistant]

All committers have signed the CLA.

[github-actions]

Warnings

⚠️

Some issues found for the commit messages in this PR: the commit message "remove other Flash size options and partitions": summary looks empty type/action looks empty Please fix these commit messages - here are some basic tips: follow Conventional Commits style correct format of commit message should be: <type/action>(<scope/component>): <summary>, for example fix(esp32): Fixed startup timeout issue allowed types are: change,ci,docs,feat,fix,refactor,remove,revert,test sufficiently descriptive message summary should be between 10 to 72 characters and start with upper case letter avoid Jira references in commit messages (unavailable/irrelevant for our customers) TIP: Install pre-commit hooks and run this check when committing (uses the Conventional Precommit Linter).

👋 Hello tangjie133, 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.
- Resolve all warnings (⚠️ ) before requesting a review from human reviewers - they will appreciate it.
- 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 f64c939

[P-R-O-C-H-Y]

Hi @tangjie133, I see that the board is shipped with 4MB flash chip. Please remove other Flash size options + partitions that does not fit in 4MB.

[tangjie133]

@P-R-O-C-H-Y Removed other Flash size options and their corresponding partitions.