fix(m5stack_tab5): Add chip variant menu

[lucasssvaz]

Description of Change

This pull request updates the boards.txt configuration for the m5stack_tab5 board, adding support for different chip variants and corresponding CPU frequencies based on the board version.

Key configuration changes:

Chip variant and frequency selection:

• Added a chip_variant field (esp32p4_es) to the m5stack_tab5 build configuration to specify the chip variant used.
• Introduced a new menu option ChipVariant with two choices: Before v3.00 (uses esp32p4_es at 360MHz) and v3.00 or newer (uses esp32p4 at 400MHz), allowing users to select the correct chip variant and CPU frequency based on their hardware version.

Related links

Fixes #12324

[github-actions]

	Messages
📖	🎉 Good Job! All checks are passing!

👋 Hello lucasssvaz, 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 c81f9ea