Settings: Refactor code to reduce complexity and dependencies

[MattHag]

The Setting class in logitech_receiver/settings contains dozens of subclasses, which are expected to contain specific properties. However, that's not ensured via implementation.

A dependency graph for the logitech_receiver module can be created via pyreverse

The existing problems are

• Complex code with many hard connections, "big ball of mud"
• Hard to maintain with several levels of subclasses
• No documentation of available/expected properties nor enforced
  • Maybe data classes to specify properties e.g. for RegisterDpi works better.

Information

• Solaar version: 1.1.13