feat(boards): update wifiduinov2&wifiduino32s3 boards setting

[i3water]

By completing this PR sufficiently, you help us to review this Pull Request quicker and also help improve the quality of Release Notes

---

Description of Change

update wifiduinov2&wifiduino32s3 boards setting

Tests scenarios

All example codes were verified on the wifiduinov2&wifiduino32s3 board base on Arduino SDK v3.2.0, confirming functionality across different scenarios.

Related links

product link:
https://www.openjumper.com/doc/wifiduino-v2
https://www.openjumper.com/doc/wifiduino32s3

[CLAassistant]

All committers have signed the CLA.

[github-actions]

Warnings

⚠️

Some issues found for the commit messages in this PR: the commit message "change wifiduino32s3 spi pin to spi1": summary looks empty type/action looks empty the commit message "fix wifiduino32s3 spi pin set": summary looks empty type/action looks empty the commit message "fix wifiduinov2&wifiduino32s3 build board error.": summary should not end with a period (full stop) summary looks empty type/action looks empty the commit message "fix wifiduinov2(esp32c3) board setting": summary looks empty type/action looks empty the commit message "fix wifiduinov2(esp32c3) cdc on boot default setting.": summary should not end with a period (full stop) summary looks empty type/action looks empty the commit message "remove 32Mb flash size": summary looks empty type/action looks empty the commit message "update wifiduinov2&wifiduino32s3 boards setting": 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 i3water, 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 c03a07b

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

PTAL on my comment.
Please also share the boards data sheets or links so I can confirm some settings.

[i3water]

PTAL on my comment. Please also share the boards data sheets or links so I can confirm some settings.

Thank you very much for your patient inspection. I have updated the incorrect settings.

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

You can remove the 4MB option as it comes with 16MB or optional 8MB as per docs. Also the 32MB can be removed.

Suggested change

	wifiduino32s3.menu.FlashSize.4M=4MB (32Mb)
	wifiduino32s3.menu.FlashSize.4M.build.flash_size=4MB

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

@i3water This is the last thing waiting on your comment :) Otherwise all looks good

[i3water]

Thank you very much, it has been modified now.