Allow more than one dynamic analysis for a single build

[reddwarf69]

I can build once with both Address and Undefined Behaviour Sanitizers (and given C++ build times I would rather keep it this way). I may even be able to run Valgrind in that same build (and tomorrow somebody could release "NoValgrind"). But CDash doesn't seem to be able to associate more than a single dynamic analysis to a build.

I can do this in CTest

set(CTEST_MEMORYCHECK_TYPE "AddressSanitizer") 
ctest_memcheck() 
ctest_submit(PARTS MemCheck) 
set(CTEST_MEMORYCHECK_TYPE "UndefinedBehaviorSanitizer") 
ctest_memcheck(APPEND ${ctest_test_args}) 
ctest_submit()

And CDash will still not take them both.

[zackgalbreath]

This is a good idea. Off the top of my head, we'll need to change the way the dynamicanalysissummary table is structured. Currently its primary key is buildid. We would probably have change this to a composite primary key (buildid, checker).