Feature/109

This PR adds a TDAF-compliant Conversion Pattern to log4j, including a transaction id. The README and some templates have been modified accordingly.

The issue #109 will be completed when all the traces are revised; this is necessary to create the alarm conditions table.
Probably a rationale about why we need booting time as transaction ID prefix is welcome... You could cut-and-paste from the explanation at Orion wiki:

> a string in the format "1405598120-337-00000000001". The transaction id generation logic ensures that every transaction id is unique, also for Orion instances running in different VMs (which is useful in the case you are aggregating logs from different sources), except if they are started in the exactly same millisecond