Refactor RuleConsequenceProcessor not to evaluate inline switch right away, but rather follow a (Template SNode)->(Runtime Counterpart) model in action throughout generator. With that, consequence can get prepared once and then applied multiple times.
Simplify RuleConsequenceProcessor - use itself instead of a dedicated Consequence.
Deprecate and refactor constructors of TemplateQueryContext and its subclasses to be uniform, forget about explicit inputNode, utilize the fact generator is accessible from TemplateContext now