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.
This was to support your original API.  Rather than deprecating it, I'd like to simply remove it since I think the spring-based configuration does everything we need and would even save a few lines of code since Spring has a facility for auto-detecting script changes.  Since the Resource script construction was not in a released version of PersonDir, do you mind if I just remove it, and thus remove this scenario?