Print stack trace when unit test check fails

This makes it much easier to see where in the unit test the check is failing.
I should have done this a long time ago.
Add <Project>_TRACE_ADD_TEST (TriBITS #47)

Now you can see what tests get added or not and why.

Build/Test Cases Summary
Enabled Packages: TriBITS, CTeuchos
Enabled all Forward Packages
0) MPI_DEBUG => passed: passed=186,notpassed=0 (1.13 min)
1) SERIAL_RELEASE => passed: passed=181,notpassed=0 (1.05 min)
Other local commits for this build/test group: f8acd75
Remove error message about no ./description file

This push hook was giving an error message about not being able to
read the ./description file (which doe not exist by default).

Here I added a test to see if that file exists before reading it and
otherwise set a dummy default.
Add default for <Project>_TRACE_ADD_TEST (TriBITS #47)

Gave <Project>_TRACE_ADD_TEST a default value of
${<Project>_VERBOSE_CONFIGURE}.
Add NUM_TOTAL_CORES_USED for TRIBITS_ADD_TEST() (TriBITS #47)

Got basic functionlity to work.  Will ned to refactor as this gets reused for
TRIBITS_ADD_ADVANCED_TEST().
Make OVERALL_NUM_MPI_PROCS behave better (TriBITS #47)

Now, not setting OVERALL_NUM_MPI_PROCS will not automatically result in
setting the PROCESSORS property to the default number of MPI proceses when
there are only CMND test blocks.  That was very bad behavior.  Now if you
don't set OVERALL_NUM_MPI_PROCS and have all CMND test blocks, PROCESSORS is
set to 1.

Also, now the PROCESORS property is set to the max of the number of MPI
processes for all of the EXEC blocks.  Before it was ony set to the *last*
block!  That was not good behavior.

I still need to implement support for NUM_TOTAL_CORES_USED for the
TRIBITS_ADD_ADVANCED_TEST() script but that is coming next.
Add 'test' to 'NOT added test' (TriBITS #47)

This makes clear that this is a test not being added.
Refactor to getting ready to print stats about added test (TriBITS #47)
Print out test properties when test is added (TriBITS #47)

This now shows the user the important details about a test like the max num of
MPI processors used, the number of processors passed to CTest, and the timeout
(if one is set).
Add [OVERALL_]NUM_TOTAL_CORES_USED to TAAT() (TriBITS #47)

I also updated all of the documentation.  The tests are pretty good I think.
Update gitdist help doc

Build/Test Cases Summary
Enabled Packages: TriBITS, CTeuchos, COBRA_TF
0) MPI_DEBUG => passed: passed=318,notpassed=0 (4.51 min)
1) SERIAL_RELEASE => passed: passed=311,notpassed=0 (3.10 min)
Other local commits for this build/test group: 80a039b, 768d9c7, e84f39d, a210684, 022a56a, 78b407b, b274299