CA scripts clean up

[nij-intel]

1. run_nightly - appends test_ every time run_nightly is run - creates files like this: test_test_test_test_M2S2_GEN2_F2F_11
2. grid scripts not cleaning up VCS db and log files
3. results is not setup to VCS runs
4. run_regression - add regression_long that will run all tests

[sameer-eximius]

#1.
the run_nightly would append 'test_' prefix 'once' each time it is run a fresh.
In case, a part commented run_nightly is seen to be running, (e.g. only result checking part) then test_ prefix addition may be observed with every iteration run.
There is a nightly result back-up and clean up part in the run_nightly script that would suffice
#2, #3
In case Intel has the proposed VCS bi-products' list to clean up, it can be added. Feel free to share
Eximius do not have VCS set-up for confirming
#4. run_nightly covers all functional cases with 0.9.7 release (94 tests)

[nij-intel]

except for run_regression the rest is resolved. Eximius will address run_regression opportunistically in the next couple of weeks after the test failures are addressed