Topic/validator options

[jordan-ayers]

I ran into a case at work where using:
validate("column-name").isUUID( { onlyNotNull: true } );
would reject an update on a loaded model with "'column-name' must be a valid UUID got null".

I don't have 'make test' working at home yet, but the logic change to enable the option was simple enough. Letting 'onlyDefined === false' override onlyNotNull in case of a conflict seemed best.

[jordan-ayers]

Test cases added and now passing on the nodejs 0.6 build on Travis.
Nodejs 0.8 build is failing in a similar fashion to my own system (running 0.10), but that issue appears to have been present before my changes.

[jordan-ayers]

Association tests pass here now if I move them to the end of the test sequence (renaming test/associations to test/z_associations). This might clean the errors on Travis, but seems a bit crude. Still have two assert errors in "patio" test sections, and am unable to run MySQL adaptor tests.

[doug-martin]

Ok so all the tests are passing Im not quite sure what was going on but while I was checking that out I updated to the latest mysql and postgres modules and update the travis tests to use v0.10 and removed support for v0.6 because of the postgres update. If you could try running this locally and let me know how that goes that would be great.