Better trace for nested jinja errors

When we have an error in a jinja macro, it is something hard to go to the real underlying template when you use extensibly macros.

this conditionnaly show the macro line when we have an error in a macro and not directly in the rendered template

Please read attached unit tests !