Concurrent version installation

[jamesmarkchan]

currently each version uses the previous version's db. Giving each new version a dedicated db will isolate data between versions allowing multiple version to be run concurrently wo the possibility of corrupting benchmark data and keep the data model clean for field installs.

currently the derby db is located at:

C:\Users\%USERPROFILE%\.jDiskMark\derbyDB

this could be updated to:

C:\Users\%USERPROFILE%\.jdm\v<version>\derbyDB

Completion Criteria:

1. installing new places the derby db in the new path
2. can run multiple versions of jdm concurrently during a demo

The downside of this is users might believe they are loosing their previous benchmarks when they install a new version so during the install it might be ideal to copy the db from the previous install to the new db location so this would be a modification to the installer.

[jamesmarkchan]

here is a test of us being able to run different versions concurrently. note this does not allow us to run multiple instances of the same version, just different versions for regression testing (helps the developers and testers). @jDiskMark/dev-team

[jamesmarkchan]

@tylermlui i merged in changes from your macOS branch since i needed the properties files being embedded into the jar. when you restart your code would be best to rebranch from dev or pull changes from dev into your feature branch. I'll merge this release branch into main and back into dev soon.