⚡ Optimize JSON property lookup using TryGetProperty in HardwareEndpoints

[spelech]

Summary

Addresses failed Jules session \17790085110777310707.

💡 What

• Replaced repeated
  oot.EnumerateObject()\ linear scans across \GetString, \GetLong, \GetInt, and \GetDouble\ helper methods in \Endpoints/HardwareEndpoints.cs\ with an optimized \TryFindProperty\ routine.
• \TryFindProperty\ first uses
  oot.TryGetProperty\ for fast (1)$ exact-cased lookups for requested parameter names.
• Retains case-insensitive property matching as a fallback for backwards compatibility.
• Added comprehensive unit test in \HardwareEndpointsTests\ verifying property lookup with alternative names and varied casing.

🎯 Why

• Previously, extracting each property triggered an (N)$ traversal over all object properties.
• With ~15 properties parsed per request on /api/hardware/evaluate, this created redundant enumeration and enumerator allocation overhead.
• Using \TryGetProperty\ directly evaluates the property hash in (1)$ time.