v2->v3 upgrade, properties files

[Rod Widdowson]

> The schema uses an enum for a
> variety of LDAP settings. So there's no way they're going to work with
> properties. I can only speculate how it worked before.

Following on waay to late.  The way that V2 did properties was (at least
architecturally) to insert a filter between the file reader and the parser &
verifier, so by the time that validation happened the "file" was schema
correct.

In V3 we let Spring deal with the properties ("Why have a dog a bark
yourself?") which meant that we needed to slacken off the schemas in several
places.