Decorator Velocity Template/Macro Cache Permanent

Limitiation of Velocity webapp loader that does not support template/macro modification detection causes decorator templates/macros to be cached permanently. A Tomcat restart or disabling of cache is required during decorator development to support hotdeploy.

This is to be fixed by switching back to a file based loader and configuring the base path using spring system property injection already in place for applicationRoot. When complete, decorator and template modification should be picked up every 10 seconds. The current Velocity Engine management logic may be changed to rely on this functionality to detect macro modifications if it can be made reliable.