Fix: config save not working (all fields saved at wrong offset)
Problem
Config_body starts with an internal config_version byte, but both the web config page and set_ds5.py expected the layout to start directly at haptics_gain. This 1-byte misalignment caused every read and write to operate on the wrong fields — settings appeared to save but had no effect, and values displayed in the config page were garbage.
Fix
The HID API (reports 0xF7 GET and 0xF6 SET) now skips config_version and exposes exactly the 17-byte layout that clients expect, starting at haptics_gain. The config_version field remains managed internally by the firmware.
Result
Config page and set_ds5.py now correctly read and persist all settings.
Also includes v1.2.2 fix: DualSense not detected by Steam on Linux.