fix(rp): reacquire same-name CDC after BOOTSEL deploy

[zackees]

Summary

• exclude known-unhealthy RP CDC devnodes from the pre-flash name snapshot
• allow a stale Windows COM selector to use an unambiguous mounted BOOTSEL volume
• reacquire a healthy runtime CDC endpoint even when Windows reuses the same COM name

Why

A phantom COM record such as COM18 was counted as already present before an RP2350 UF2 flash. When the board returned healthy on COM18, post-flash discovery filtered it out solely because its name had not changed, so deploy returned no application port and AutoResearch could not continue.

Validation

• focused regression test: RED before helper, GREEN after implementation
• bash test -p fbuild-deploy — 288 passed, 13 ignored
• soldr cargo fmt --all -- --check
• soldr cargo clippy -p fbuild-deploy --all-targets -- -D warnings
• full bash test
• pre-push review clean
• hardware HIL pending completion of the coordinated FastLED run

Closes #1404
Coordinated with FastLED/FastLED#4062.

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

---

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.}