Add Arduino USB PID supplement

[zackees]

Summary

• add fetch_arduino_usb_pids.py to parse official ArduinoCore boards.txt VID/PID rows for Arduino VIDs 2341 and 2a03
• cover AVR, SAM, SAMD, megaAVR, mbed, Renesas, and Zephyr official Arduino cores without downloading large board-package archives
• wire the fetcher into the nightly USB merge before generic USB-ID feeds so first-party Arduino product names win
• document that ArduinoCore board-package rows improve VID/PID resolution but do not prove local fbuild board support unless the board exists under crates/fbuild-config/assets/boards

Source notes

• Arduino does not publish a single public PID registry; the official core boards.txt files are the public source for product PID rows.
• Live fetch smoke emitted 136 Arduino PID rows.
• Spot checks: 2341:0072 Arduino Nano Matter, 2341:1002 Arduino UNO R4 WiFi, 2341:0266 Arduino Giga R1, and 2a03:0043 Arduino UNO.

Closes #734

Validation

• uv run --no-project --with pytest pytest online-data-tools/test_arduino_usb_pids.py -q
• ruff check online-data-tools/fetch_arduino_usb_pids.py online-data-tools/test_arduino_usb_pids.py
• actionlint .github/workflows/update-data.yml
• git diff --check
• live fetch smoke: fetch_arduino_usb_pids.py emitted 136 rows from official ArduinoCore sources

[coderabbitai]

Warning

Review limit reached

@zackees, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 38 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: fa83705a-4a55-43db-b78d-118d924c8c1c

📥 Commits

Reviewing files that changed from the base of the PR and between 4d87789 and 3819f39.

📒 Files selected for processing (4)

• .github/workflows/update-data.yml
• online-data-tools/README.md
• online-data-tools/fetch_arduino_usb_pids.py
• online-data-tools/test_arduino_usb_pids.py

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/arduino-usb-pids

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}