Added some utility functions for, and documentation about, trigger types used in integtests

[bieryAtFnal]

Description

It is not always easy to determine which trigger type(s) are used in which integtests, nor how to specify the parameters for a given trigger type in a new integtest.

The changes in this PR attempt to help with that, and they provide several utility functions that can be used to enable Fake HSI triggers and/or set basic parameters associated with FakeHSI and/or RandomTriggerCandidateMaker triggers. This PR also include some preliminary documentation about which triggers are used in which integtests.

This PR is correlated with ones in several other repos:

• Updated the integtest to get the basic_checks function from the utility_functions file… crtmodules#38
• Modified integtests to make use of new utility functions for setting trigger config params daqsystemtest#325
• Modified integtests to make use of new utility functions for setting trigger config params dfmodules#491
• Modified the integtest to make use of new utility functions for setting trigger config params trigger#434

To test these changes, the following steps can be used:

DATE_PREFIX=`date '+%d%b'`
TIME_SUFFIX=`date '+%H%M'`

source /cvmfs/dunedaq.opensciencegrid.org/setup_dunedaq.sh
setup_dbt latest
dbt-create -n NFD_DEV_260624_A9 ${DATE_PREFIX}FDDevIntegtestTriggerChoices_${TIME_SUFFIX}
cd ${DATE_PREFIX}FDDevIntegtestTriggerChoices_${TIME_SUFFIX}/sourcecode

git clone https://github.com/DUNE-DAQ/crtmodules.git -b kbiery/integtest_trigger_choices
git clone https://github.com/DUNE-DAQ/daqsystemtest.git -b kbiery/integtest_trigger_choices
git clone https://github.com/DUNE-DAQ/dfmodules.git -b kbiery/integtest_trigger_choices
git clone https://github.com/DUNE-DAQ/hsilibs.git -b develop
git clone https://github.com/DUNE-DAQ/listrev.git -b develop
git clone https://github.com/DUNE-DAQ/snbmodules.git -b develop
git clone https://github.com/DUNE-DAQ/trigger.git -b kbiery/integtest_trigger_choices
cd ..

cd pythoncode
git clone https://github.com/DUNE-DAQ/integrationtest.git -b kbiery/integtest_trigger_choices
cd ..

. ./env.sh
dbt-build -j 12
dbt-workarea-env

dunedaq_integtest_bundle.sh --verbosity 2 -r local --random 5

Type of change

• Optimization (non-breaking change that improves code/performance)

Testing checklist

• Full set of integration tests pass (dunedaq_integtest_bundle.sh)

Further checks

• Code is commented where needed, particularly in hard-to-understand areas

[MRiganSUSX]

Hi @bieryAtFnal,
Thanks for this updated, much cleaner, functionality.
I'm leaving several suggestions here and across the linked 5 PRs.

Don't think there are any glaring problems, some small style things and some places that could be tidied up.

[MRiganSUSX]

This documentation is GREAT.
My only concern is whether it makes sense to have the year in the filename instead (completely ok in the text), as updates later on can cause link breaks, or the file may look like it obsolete later on.

[bieryAtFnal]

We can discuss.
I put the date in the filename to try to make it very clear that it is a snapshot and may not be up-to-date at some point in the future...

[MRiganSUSX]

Thank you for addressing the comments.

Passes the whole dunedaq_integtest_bundle.sh.