AutoValue unsoundness, Test Suite runner, Paths with spaces

[superaxander]

This PR adds an error for a case where AutoValue was unsound namely when it was combined with other permission resources for the same field which could result in permission amounts greater than 1 (but in a way where you could still call the method erroneously without warning if you disabled smoke checks) At first I thought simply adding an implication perm(a.f) == none ==> Perm(a.f, read$()) would fix the issue since that prevents you from getting more than write permission, however we can then no longer perform the leak check. I might try later to see if I can do something like \old(perm(a.f)) == none in the postcondition to conditionally add the leak check when necessary, this would still mean restricting the order in which the permissions may appear. (AutoValue must come after the normal permission resource statements)

Additionally this PR also adds bin/testSuite which you can use to run the entire testSuite or specific test cases from the command line. To run all tests simply run bin/testSuite, to run a specific test class run bin/testSuite -s vct.test.integration.examples.AutoValueSpec replacing the class with your test class, or to run a specific test using its name (or part of its name use bin/testSuite -s vct.test.integration.examples.AutoValueSpec combination. (this last command runs the test added by this PR whose name contains the filename combination.pvl which we can match on with -z) Full usage details are here: https://www.scalatest.org/user_guide/using_the_runner

Finally this PR also updates the runner scripts (on linux at least) and the classpath files (on all platforms) to work when VerCors is run from a path containing spaces.