feat(import): support jlcpcb identifiers in import flow

[techmannih]

Summary

This PR updates the import flow to understand and display provider-prefixed JLCPCB identifiers.

It is intentionally scoped separately from the search formatting change in #3118.

Why

After adding jlcpcb:C... identifiers to CLI search output, the import flow still had two gaps:

• direct JLCPCB imports only parsed raw C... or numeric part numbers
• interactive import selection still displayed raw C... values instead of the provider-prefixed identifier

That made the search -> import workflow feel inconsistent and made the identifier format harder to use end-to-end.

What changed

• accept jlcpcb:C1234, C1234, and bare numeric part numbers in direct JLCPCB import parsing
• show jlcpcb:C... identifiers in JLCPCB import selection labels
• reuse the same identifier formatting in import progress messages
• centralize JLCPCB part-number normalization and component display helpers used by import
• add focused tests for direct part parsing and import choice formatting

User impact

• tsci import jlcpcb:C2040 now works
• tsci import C2040 and tsci import 2040 continue to work
• JLCPCB choices shown during tsci import now use the same provider-prefixed format users see elsewhere

Validation

• bun test tests/cli/import/parse-direct-lcsc-part-number.test.ts tests/cli/import/format-jlcpcb-import-choice-title.test.ts
• bunx biome check cli/import/register.ts cli/import/parse-direct-lcsc-part-number.ts cli/import/format-jlcpcb-import-choice-title.ts lib/shared/jlcpcb-part-number.ts lib/shared/jlcpcb-component.ts tests/cli/import/parse-direct-lcsc-part-number.test.ts tests/cli/import/format-jlcpcb-import-choice-title.test.ts

[seveibar]

Add representative usage

there appear to be unrelated changes?

[seveibar]

Or snapshot output, not sure i understand what you’re doing because there is no proper integration test