Test automation identity

Sorry for this rather large pull request but it could not really be avoided as I am converting the integration test to a SBT multimodule project so that I can share code for an upcoming identity test module. To do that I had to update the Scala framework and use the latest version which included some other changes, such as multibrowser support.
> The setProperties method changes the set of system properties for the current running application. These changes are not persistent. That is, changing the system properties within an application will not affect future invocations of the Java interpreter for this or any other application. The runtime system re-initializes the system properties each time its starts up. If changes to system properties are to be persistent, then the application must write the values to some file before exiting and read them in again upon startup.

Given that I don't see what harm it can do.

I would maybe just modify this so it does not mess with a command line argument...

    if (the property is not set) {
       setTheProperty() 
   }