Add v1.8 Force variant and BC711 validation

[hrx114514x]

What changed

• add PC711ProbeForce.kext as a parallel opt-in build that matches NVMe class 01:08:02 without a PCI Vendor/Device gate
• retain the recommended PC711Probe.kext with its existing 1C5C:174A restriction
• deliberately share one bundle identifier so the variants are mutually exclusive
• record successful BC711 HFM512GD3JX016N and HFM512GD3JX013N tests
• bump the project to v1.8.0 and add bilingual installation, scope, changelog, and release documentation
• build and statically distinguish both Kexts in CI

Why

The standard matcher now has successful evidence on both PC711 and BC711 devices sharing the 174A controller identity. The Force artifact provides an explicit fallback for affected NVMe devices that expose another PCI ID, without widening the recommended default build.

Validation

• Scripts/verify.sh builds and checks both x86_64 Kexts
• standard binary retains 1C5C and 174A comparisons
• Force binary contains neither comparison and matches only NVMe class 01:08:02
• both Info.plists lint and both binaries retain Darwin 20-24 boundaries
• release ZIP contents and SHA-256 sums verified