map-style deserialiser output

[RalphSteinhagen]

map-style deserialiser output

presently: class -> wire-format -> class

do we have a strong use-case for this?
pros:

• support of more flexible run-time declared use-cases?
• AK: -> separate deserialiser anyway, added later on

cons:

• more coding (nested unordered_map<std::string, unordered_map<...>> (probably need to use std::any a lot) -> least constexpr-ness
• AK: if we allow services to use this dynamic interface, the API evolution issue becomes a lot more complicated -> deserialisation only?
• how many strong (<-> sort of mandatory) or frequent (80/20 rule) use-cases do we have?
  1. generic top-level UIs that can subscribe/get/set to any service (opencmw-explorer)
  2. AK: needed for potential python integration (else we have to dynamically compile opencmw c++ code from python, can be done but involves a lot of complexity)

Application: interface to Python to be evaluated