The path should now always resolve to the same as the one where the FanControl.Liquidctl.dll is

…("Fan 1 speed", "Fan 2 speed", etc)

- I probably violated a dozen of best practices though
- Fixed a bug where status values that are not numbers/floats prevented the plugin from working
- Replaced the hardcoded location of the liquidctl.exe to match the directory where the FanControl.Liquidctl.dll is located. So you can now also install the plugin over the Fan Control interface