fix(board): support for pre/post v3 esp32p4 for 4D Systems MIPI Display modules

[cruzjuniel]

Description of Change

This provides the option to select the ESP32-P4 chip variant (pre v3 and post v3) by specifying the hardware revision of 4D Systems MIPI display modules.

With the recent change in chip variants, esp32p4 changed to esp32p4_es and newer/upcoming v3 chips utilizing esp32p4, the current boards options default to >= v3.x chips, which wont work with existing boards that uses v1.3.

Test Scenarios

We've tested this change using the current latest code v3.3.6

Related links

N/A

[github-actions]

	Messages
📖	🎉 Good Job! All checks are passing!

👋 Hello cruzjuniel, 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 4d77993