HIVE-29401: Speed-up Derby operations by setting durability mode to test

[zabetak]

Why are the changes needed?

To speed up all tests using a file-system backed Derby database by avoiding expensive I/O operations. More details under HIVE-29401.

Does this PR introduce any user-facing change?

No, this is a test only change.

How was this patch tested?

Picked randomly a few q files that use Derby and checked that property takes effect by searching in the derby.log file.

mvn test -Dtest=TestMiniLlapLocalCliDriver -Dqfile=jdbc_handler.q -Pitests -pl itests/qtest

grep -a "durability" itests/qtest/target/tmp/derby.log 
Warning: The database is booted with derby.system.durability=test. In this mode, it is possible that database may not be able to recover, committed transactions may be lost, database may be in an inconsistent state. Please use this mode only when these consequences are acceptable  
Warning: The database is booted with derby.system.durability=test. In this mode, it is possible that database may not be able to recover, committed transactions may be lost, database may be in an inconsistent state. Please use this mode only when these consequences are acceptable  

[abstractdog]

big +1, thanks @zabetak for this effort! small change, but how much headache before...
we don't rely on derby consistency at all in the event of e.g. JVM crashes (if it crashes, let it go), so this is a 100% safe way to boost our unit tests' performance, I wish we had found this option before

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[zabetak]

Many thanks for the review @abstractdog and for all the underlying work on our internal ticket for getting down to this and discovering that I/O operations can be very expensive in certain settings.