Unit tests for petascopedb triggers, utilities and migration script

[Piero Campalani]

The ongoing development of a new schema for petascopedb (psql=# \dt ps9_*) is creating additional triggers, supporting functions, SQL macros, and a migration scripts for existing coverages in the PS_* tables.

Due to the big body of .sql scripts currently implemented, unit tests are highly desirable.

See:

$ git log --oneline -1
afcebaa ticket:494 - Merge branch 'feature_PetascopeSecore' into master.
$ find ./applications/petascope/src/main/db/ -name "*9*"
applications/petascope/src/main/db/README9
applications/petascope/src/main/db/petascope9
applications/petascope/src/main/db/petascope9/migrate9.sql
applications/petascope/src/main/db/petascope9/populate9.sql
applications/petascope/src/main/db/petascope9/triggers9.sql
applications/petascope/src/main/db/petascope9/schema9.sql

[abeccati]

I think priority should be given to systemtests, unit testing it fine but lets get to reliable system ones first (scheduling to Future), also seems suitable for a beginner with some guidance (and lots of patience)

[abeccati]

And SQL knowledge of course