fix(boards): Remove port property assoc. for non-unique VID/PID pairs

[per1234]

Description of Change

The Arduino boards platform framework allows properties of a port to be associated with a board definition. The Arduino development software will identify a port having the associated properties as that board.

This should only be done for properties that are unique to the ports produced by that board model. In cases where a board model does not produce a port with properties unique to that model, it is irresponsible to associate those properties with the board definition as this will cause other models to be inappropriately identified.

The authors of these board definitions associated them with non-unique USB VID/PID pairs so those associations must be removed. The 303a:1001 VID/PID pair is of the hardware CDC serial port of the native USB ESP32 chips. The others are stock VID/PID pairs of general purpose USB to serial bridge chips that are used on many different board models.

Tests scenarios

Compile for the modified boards using the platform (at 0b8eede) with this patch (0a8c586) applied.

Related links

Originally reported at https://forum.arduino.cc/t/i-dont-have-elecrow-crowpanel-7-0p/1293026

• ESP32S2 Dev Module detected ad Deneyap Mini #6384
• random board name appended to Arduino Port menu listing #7292
• There are many non-unique VID/PID pairs in boards.txt #9702
• https://forum.arduino.cc/t/issue-with-arduino-cloud-device-recognition-esp32-dev-module-detected-as-lilygo-t-display/1295971

[github-actions]

	Messages
📖	🎉 Good Job! All checks are passing!

👋 Hello per1234, 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.
- 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 91f0605