Alternative approach for defining named UDFs.

See branch: spike/340
Package: au.csiro.pathling.sql.udfs;

This approach uses annotations rather then Spring beans and my be more appropriate if these the UDFS (such as datetime or quantity operations) needed to be exposed from python interface.

Also UDFs should be more focused on unit testing the UDF operations themselves rather that the FhirPaths that use them. Or at least it would be probably easier to write more through tests cases for the UDFs (regardless if they are beans or functions) than for FhirPaths. And also I assume that in the future we my want/need to expose these UDFs in the python API (so perhaps they should be tested independently from FhirPaths).

Start with branch spike/340 and package au.csiro.pathling.sql.udfs; compare annotation-based UDF definitions with the Spring-bean approach. Review how datetime and quantity operations are exposed and how their tests relate to FHIRPath tests. Done means a decided, independently tested UDF approach suitable for possible Python exposure.