Implement "code generation evaluation" in the UFL visitor

In the light of the component-wise treatment implemented in !160 (closed) another topic becomes increasingly important: Expressions should - if possible - be evaulated at code generation time. This can lead to many collapsing structures, which greatly benefit the total amount and complexity of the generated code. Affected handlers: Max, Min, conditional, all comparisons (and probably some more)