Deprecate use of physical ranges

[akhilles]

Note

Medium Risk
Broad type migration affecting unit parsing/comparisons and all callers; risk is mainly subtle behavior changes in range containment/diff logic used by BOM matching and electrical checks.

Overview
Deprecates builtin.physical_range usage by replacing VoltageRange/ResistanceRange/PowerRange (and other *Range types) with the corresponding toleranced physical_value types across BOM helpers, generic matchers, interfaces, and checks.

Updates TVS and LED/resistor helper constructors and matching/tests to use Voltage/Resistance/Power directly (including converting single-value voltages into explicit min/max ranges), and adjusts Power/Ground net types plus voltage_within to accept Voltage instead of VoltageRange.

^{Written by Cursor Bugbot for commit 548579c. This will update automatically on new commits. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}