Test procedures for Administrative actions likely in production

[brettkettering]

Work on some test procedures to change things on repos that we expect we might change in production: iperms, bperms, and quotas. Also, test procedures for adding new namespaces. I'm not sure if these can be integrated into the Jenkins infrastructure, but consult with George. If it's possible, let's do that once you've implemented and verified these tests.

The plan is to create a simple script that takes in a list of expected operation failures (i.e. fuse_chown (success), ..., pftool_write (fail), etc. ) and compares to the operation results. Once we create a restricted Jenkins namespace (and corresponding gpfs-fileset), it should then be fairly simple to write test cases for a variety of permission permutations and quota values.