fix: update Waveshare ESP32-C6-Zero naming and default CDC settings

[eMUQI]

Description of Change

This PR updates the board definition for Waveshare ESP32-C6-Zero to improve out-of-the-box usability and consistency.

1. Enable CDC on Boot by default
   This board relies on native USB for serial communication. With the previous default setting (from feat(board): add support for Waveshare ESP32-C6 Zero #12116) , the serial monitor is not active immediately after flashing. This update changes the default to Enabled, ensuring that Serial.print() works out-of-the-box as users expect.
2. Update board name for better consistency with other Waveshare products

References:

• Waveshare Wiki: ESP32-C6-Zero
• Schematic

Test Scenarios

Not tested yet, but it should work

[github-actions]

	Messages
📖	🎉 Good Job! All checks are passing!

👋 Hello eMUQI, 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 8ceb3f1