Added the TA start, end, and activity times to the 'Emitting TA' debug statement…

[bieryAtFnal]

…in TriggerActivityMaker.

I found this additional information very useful when trying to understand the correlations between prescaled TAs from different sources, so it seems reasonable to make it a standard part of the code.

To test this change:

• create a software area based on a recently nightly build (e.g. here)
• add the triggeralgs repo to that software area and check out the kbiery/tam_debug_additional_info branch in that repo; rebuild the software
• export TRACE_FILE=$DBT_AREA_ROOT/log/${USER}_dunedaq.trace
• tonM -n TriggerActivityMaker.hpp DEBUG+10
• pytest -s -k TPG -p no:cacheprovider ${DAQSYSTEMTEST_SHARE}/integtest/readout_type_scan.py
• tshow | tdelta -ct 1 | grep Emitting | head

[aeoranday]

LGTM.