Add option to configure interactive states for components

[SirPepe]

Simple component without states:

{
  "name": "Navigation",
  "source": ".navigation"
},

Simple component with an additional state (state is just a simple selector):

{
  "name": "Navigation",
  "source": ".navigation",
  "states": [ ".navigation.open "]
},

Not so simple component with an additional state (state is a mapping for target and source, one object for each state):

{
  "name": "Navigation",
  "source": ".navigation",
  "target": "nav",
  "states": [{
    "source": ".navigation.open",
    "target": "nav.activated"
  }]
},

Before this gets added it should be demonstrated that a simple selector like nav.activated can be turned into a function that can set the element into the state described by the selector

[drublic]

Is the state meant to be triggered on a component? So do classes get applied to the component?
It think this should not be the case.

The state is thus just a description of a specific variant of the component. So it could be more like a variants array which could contain more than just states. For example you could describe different variants of a single component "button".
These variants might be treated as separate components though.
Sounds more like syntactic sugar for the config than a backend implementation, right?