The new `check-cargo-patches.sh` script verifies that all
[patch.crates-io] and [patch.'<URL>'] sections in the local
sources' Cargo.toml files actually resolve to the expected
local fork paths. It does this by running `cargo metadata`
on each source's workspace and checking that the
resolved source URL (or manifest_path for path-deps)
matches the expected local fork path.
This is the Phase J / Improvement C verification step
that the user explicitly requested: 'Build system must
report complete when upstream have our patches applied.'
The script handles the known-large workspaces gracefully:
* relibc is explicitly skipped — its [patch] section is
only the cc-rs git branch override (no `path` patches),
and `cargo metadata` on relibc takes minutes (hundreds
of deps) which would hang the script.
* All other `cargo metadata` calls are wrapped in a
30-second timeout.
Hardware-agnostic: works on any Red Bear OS checkout
regardless of which OEMs are added to the local sources
(Phase I/II/J DMI matches).
