OmenMon v1.3.4: RPM Glitch & Auto-Cal Sanity Checks

This hotfix addresses a rare hardware-read anomaly that caused impossibly high RPM readings and introduces a smart new safeguard to the Auto-Calibration engine.

🛠️ Fixed & Improved

• The "50,000 RPM" Ghost Fan Fix (#26): Fixed an edge-case where a transient 1-byte shift during an Embedded Controller (EC) read caused the Auto-Calibration Wizard to lock onto random memory noise, resulting in wildly inaccurate fan speeds (e.g., 50k+ RPM).
• HP Omen (8DD0) Native Support: Added the 8DD0 (2024/2025) motherboard directly to the native database using the standard 0xB0/0xB2 RPM layout. Owners of this model get flawless fan readings out of the box without needing to run the calibration wizard.

⚙️ Under the Hood (Core Engine Upgrades)

• Auto-Calibration Sanity Checks: The core engine (AutoCal.Load) now performs a mathematical sanity check on generated sidecar files. Across all known HP boards, the CPU and GPU tachometers sit within a few bytes of each other. If OmenMon detects that a saved sidecar has offsets that are unnaturally far apart (>16 bytes) and a native profile already exists for the board, it treats the sidecar as a read-glitch misfire. It will automatically delete the corrupt OmenMon-AutoCal.xml file and safely fall back to the native database, preventing bogus RPM offsets from getting pinned.
• Architecture Cleanup: Safe-guarded the WMI-failure edge cases to ensure valid sidecars are never accidentally deleted if the WMI lookup glitches during startup.

Huge thanks to @DreamStare0 for providing the exact "before and after" hardware probes needed to spot the byte-shift!

What's Changed

• add board 8DD0 to database by @seakyy in #27

Full Changelog: v1.3.3-reborn...v1.3.4-reborn