[Bug]: Tests can't run because they import non-existent code

Description

An example of what I'm talking about is if, given a set-up DUNE DAQ environment, you run:
pytest -s $SNBMODULES_SHARE/integtest/snb_1node_1app_rclone_http_system_quick_test.py
you'll see

/cvmfs/dunedaq-development.opensciencegrid.org/nightly/NFD_DEV_260209_A9/spack-0.22.0/opt/spack/linux-almalinux9-x86_64/gcc-14.3.0/snbmodules-NFD_DEV_260209_A9-lf4vmddtwgjzfhsmzi526f6xa5c7ahg3/share/integtest/snb_1node_1app_rclone_http_system_quick_test.py:13: in <module>
    import integrationtest.config_file_gen as config_file_gen
E   ModuleNotFoundError: No module named 'integrationtest.config_file_gen'

and rather than pass or fail, the test simply won't execute. The reason is that it's trying to import code from integrationtest which used to exist (python/integrationtest/config_file_gen.py) but was removed in September right before v3.0.1 of integrationtest was cut. This test (and any others with similar problems) should be updated to account for last year's changes to integrationtest.

Steps to reproduce

[set up daq-buildtools as usual, then]

dbt-setup-release -n last_fddaq
pytest -s $SNBMODULES_SHARE/integtest/snb_1node_1app_rclone_http_system_quick_test.py

Version and environment

NFD_DEV_260209_A9

Impact

Small/Isolated

Anything else?

No response

Start with integtest/snb_1node_1app_rclone_http_system_quick_test.py and reproduce the missing integrationtest.config_file_gen import using the documented pytest command. Search the other integration tests for similar imports and account for the integrationtest changes before v3.0.1. Done means the affected tests collect and execute instead of stopping with ModuleNotFoundError.