Added variant for Waveshare ESP32-S3-Zero

[Y1hsiaochunnn]

Description of Change

Added variant for ESP32-S3-Zero with RGB Light

Tests scenarios

Untested, pin definition is based on information in Waveshare wiki.

Related links

Wiki For ESP32-S3-Zero

Pending USB VID PR: espressif/usb-pids#174

[github-actions]

	Warnings
⚠️	Some issues found for the commit messages in this PR: the commit message "Added variant for ESP32-S3-Zero": summary looks empty type/action looks empty the commit message "Added variant for ESP32-S3-Zero": summary looks empty type/action looks empty the commit message "Fix the partition without ota": summary looks empty type/action looks empty the commit message "Fix waveshare esp32-s3-zero partition table, add 4MB partition content": summary looks empty type/action looks empty the commit message "Fix waveshare esp32-s3-zero partition table, add 4MB partition content": summary looks empty type/action looks empty the commit message "Fixed CI failures due to I2C and SPI pin definitions": summary looks empty type/action looks empty the commit message "Fixed custom partitions": summary looks empty type/action looks empty the commit message "Update tools/partitions/max_app_4MB.csv": summary looks empty type/action looks empty the commit message "change boards.txt": 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 20 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).
⚠️	Please consider squashing your 13 commits (simplifying branch history).

👋 Hello Y1hsiaochunnn, we appreciate your contribution to 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 2521a8a

[Y1hsiaochunnn]

Hi @P-R-O-C-H-Y ,
how does it look now?

[Y1hsiaochunnn]

Fixed

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

@Y1hsiaochunnn Also move the partitions from variant folder to tools/partitions.
Renaming to something like max_app_4MB and ota_nofs_4MB. Thanks

[Y1hsiaochunnn]

i did it so,network is not good, so I amend it repeatedly

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

@Y1hsiaochunnn PTAL

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

LGTM :)