add valgrind and memcheck_all into test suite

Some of our users run memory debuggers against their application and its dependencies. This turns up any memory leaks, uninitialized memory, and buffer overruns we may have in SCR or its libs. We should add these tests to our own release process to save them the trouble.

Start by locating the SCR release process and existing test-suite entry points, then identify how dependencies are built and tested. The work is done when Valgrind and memcheck_all are integrated into the release tests and can check SCR and its libraries for memory errors.

Written by the indexing model from the issue text.