fix #10671: make server handling of odd file paths more configurable

Fixes https://trac.openmicroscopy.org.uk/ome/ticket/10671 by splitting file path naming rules into separate combinable sets whose application is server-configurable, and by having the server reject violations instead of fixing them.

One way to test would be to build the server locally after changing `omero.fslite.path_rules` in `etc/omero.properties` to,
```
omero.fslite.path_rules=Windows required, UNIX required, Windows optional, UNIX optional
```
and to name images in ways that break those "optional" rules, like `-image.tif` or `image.tif.` or suchlike to make sure that a server exception is thrown on import. (Also, sensibly named images should still be importable!)

Writing meaningless garbage in `omero.fslite.path_rules` should cause a server exception in the blitz log.

(Clients using `ImportLibrary` ignore the `omero.fslite.path_rules` setting and automatically fix names that break the "required" rules; in a further PR they may be changed so as to not do any auto-fixing at all, it is a trivial code change.)