Configuration driven device and scene definitions.

[amarek]

See https://github.com/amarek/OMOTE-Firmware/blob/config/config.md for description of the changes.

[KlausMu]

Thanks, @adam-marek , for this PR. It looks really promising. Please give me some time to look through all of this. Currently I am a little bit busy ...

[amarek]

No worries, take your time. In general I view these changes as the first step towards having OMOTE configurable via a web/desktop app. We just need the app to spit out the YAML config which then could be pulled into OMOTE at runtime (over MQTT, http, etc.) instead of having it compiled into the binary.

BTW, I saw some CI failures above which resulted from PlatformIO not having the PyYAML package in its standard environment - just added automated install for that package.

[amarek]

Added conditional compilation for config sources so that the legacy configuration (no YAML_CONFIG defined) still compiles with the config dependencies missing.

[amarek]

The mingw64 fail above does not seem related to my changes ....

[KlausMu]

No, not related to your changes. The way the action has to be defined changed. I fixed it in main, but in your branch it is still the old way, which fails. But you can ignore it, since the other builds are successful.