Hhd

This release includes under-the-hood updates for the built-in http server, a bug fix, and a new feature.

*Features:*
- The new feature today is a plugin blacklist. As hhd ventures into more configuration domains, you might decide that it should not control a certain aspect of the device. In this case, you can disable the relevant plugin.
- This is opt-out as it is more intuitive from a user perspective to have all installed plugins load on first launch.
- HHD will never modify device settings (that do not revert when it closes) without your consent or without being instructed to.
- The HTTP endpoint of HHD can now serve a UI and includes a simple non-functional one in this release.
- This means that you will be able to tweak HHD settings from your browser soon! From your Go or another computer (!).

*Bug Fixes:*
- The virtual uinput/evdev device introduced in the previous release still hooked the touchpad, which made it not work. This is no longer the case.
- A pull request was made to libretro with the controller configs for HHD. When it gets accepted, Retroarch will work correctly by default!

This is a semi-major release with 2 new features and 3 bug fixes.

*Features:*
- a new virtual controller type is added that uses UInput.
- No more PS glyphs in steam!
- This controller has full support for all legion go buttons (incl. back buttons).
- If gyro is enabled, a second Motions Device is added, in the same way it is added by the playstation, joycon drivers. This device is supported by at least dolphin and a udev rule is included to enable it. However, it is not broadly supported yet (very new).
- HOWEVER: Steam does not support the back buttons, gyro for this controller type. This is why the initial/default controller is a DS5.
- the http API is fleshed out to include get/set/del commands, proper security token support, and the API docs were created (`docs/http.md`). This marks the first version of HHD with a proper HTTP API! (still disabled by default).

*Fixes:*
- disabling LED support for the DS5 controller was fixed.
- the options for disabling controller emulation and disabling controller shortcuts were implemented.
- a variety of permissions issues that led to parts of the config directory being owned by root were fixed. HHD will fix the permission issues for the affected folders automatically.

This release changes the HTTP API to run under `/api/v1` instead of `v1` to free the namespace of the endpoint for a potential GUI that is served under hhd (e.g., in `http://localhost:5335`). It is a proactive change to avoid issues in the future.

In addition, it changes the automatically generated token to only be generated once and then read back from `~/.config/hhd/token` and to only be 12 characters long. This allows the user to remember the token and to change it if they wish.

The command `hhd token` is added to display the generated token in the terminal, so the user can copy it after setup.

This command can be ran as the user: `hhd token` or as root `sudo hhd --user $(whoami)`.

Fixes a bug which caused the HTTP server to start regardless of the config option.

The HTTP server should be disabled by default in the v0.2 series.

This version of HHD adds two major features:
- controller hiding, which fixes most issues with emulators right now
- it uses a very stable method that was found to cause no issues
- a profile system and HTTP API for HHD that will allow configuring it from a GUI

Both of these features required reworking the event loop of HHD and the config structure. This unfortunately means that you will need to reconfigure HHD again, using the new `state.yml` file.

Also in this release, we switch to automated github workflows and a release note, which should which features change clearer.

Versions `v0.1.11` and `v0.1.10` are extremely stable and have feature parity for this release, so you may opt to skip `v0.2.0`.

Known issues:
- the shortcut and xinput mode options in the config have not been implemented yet and are ignored.

There was a signature check introduced on 6.2 that made the driver unavailable on 6.1. A new version check allows the driver to work both on kernels before 6.1 and after.