Hi @loostro,

I agree this changes should not be in this "feature" PR.

But, it's just for making templates easier to read. Currently, generated templates are sometimes difficult to read especially concerning block and end block definition. Before, we got:
```twig
{% block my_awesome_block %}...{% block my_awesome_second_block %} ... {% block another_one %} ...

{% endblock %} ...
...
{% endblock %} ... {% endblock %}
```

Now we got:
```twig
{% block my_awesome_block %}...{% block my_awesome_second_block %} ... {% block another_one %} ...

{% endblock another_one %} ...
...
{% endblock my_awesome_second_block %} ... {% endblock my_awesome_block %}
```
This seems stupid in this example, but in admin generated templates, I sometimes loose some time to clearly identify where a block really ends (especially with big blocks).

I know these two modifications are not BC break because:
 - modification in getEchoBlock doesn't change how block is rendered (I just keep in memory the block name)
 - modification in getEchoEndBlock could effectively introduce an error, but if an error happened, it means that template definition is wrong.

I just have to correct unit test now I've made this change, and adding some to be sure that getEchoEndBlock always work.

I'm opened to talk about that :)