History Directive Rewrite

New implementation details:
- Almost all render functions are idempotent (not mutates dom, only renders the template)
- It should perform better, because it uses much less operations that original implementation.
- Works as component and self-contained, and not requires additional boilerplate in each page that is used (removes a lot of duplicated code from controllers, directives and templates).

The main reasons for rewrite history directive:

- the original implementation is done with full mutable implementation, having functions that always mutate the dom, that is very error susceptible and implies very unclear code to simple review.
- the original implementation uses dom mutation instead string rendering, that is usually is slow.
- the original implementation implies a lot of boilerplate in each template where is used. With new implementation is works like single, self-contained component.
- the original implementation implies a lot of boilerplate in each controller and directive of userstory, issue and task details. 

This pr includes fixes for that related issues:
- #812 [UX] Orden cronológico inverso en comentarios (removing unnecesary nested html structures)

NOTE: this is complete rewrite and can contain regressions, it should be well tested before merge.