Persondir 78 enhance groovy person attribute dao

Several notes:
* Allows easy configuration by Spring
* Implemented suggestion from Misagh to switch from configuring a method to execute to the script implementing an interface.  Though it makes the Groovy script more complicated since it has the baggage of class construction, I think it is generally better as it is with the spirit of the DAO class, and many Groovy implementations will require configuration passed into them anyway so I don't think it is overly burdensome.  I did add a BaseGroovyScriptDaoImpl class to make the Groovy scripts less cluttered.
* I deprecated the original interface.  After having found that Spring provides a facility to detect changes in groovy source files, I really don't see much value to it and would like to remove it (but haven't yet).  I am open to other's thoughts on whether to leave it.  I did modify it to be much more efficient so the groovy source is not parsed every time just to have dynamic capability.  I did have to fix the modified-reload logic so it was quite an interesting and educational experience even if we delete it!  :smile: 
* Beefed up the test script.
Hmmm... Since I took your suggestion and made the interface a class instead of an arbitrary method (default to run) it would be awkward to try and support both.  I will split my class into a separate class and we can simply delete the old groovy class at another time.  Another important note about the old interface is that we cannot pass the logger into the script because you can get get classloader exceptions if you attempt to use the logger.  A separate groovy attribute dao class is a bummer but it is probably the best way to go.