Unexpected behavior of context.getTemplateName()

Nobody has claimed this yet.

Consider a template named `a.html`;

~~~~
Some literals
// inside a helper calling context.getTemplateName() results in 'a.html'
{> "b.html" /}
Some more literals
// inside a helper calling context.getTemplateName() now results in 'b.html'
~~~~

I think invoking context.getTemplateName() should always return the name of the template that is currently rendered, i.e. `a.html` in all cases shown above and `b.html` when invoked inside `b.html'.

Start by reproducing the example with a.html, the helper calling context.getTemplateName(), and the included b.html template. Inspect how getTemplateName tracks the current render context; done means it consistently returns a.html from the helper in this case and b.html when called within b.html.

Written by the indexing model from the issue text.