Fix bug for allowed truncation collections without Aux

There was a bug included to allow the truncation of collections, which prevented the serialisation of the Aux collections allowed for truncation.

Seen in various repro, flagged in ATR-29387 and ATR-29384.

Tested with:

• CI test: Trigger_athenaHLT_v1PhysP1, checking that the flagged collections are still present with trigbs_dumpHLTContentInBS_run3.py --hltres --sizeSummary data....
• test_trigP1_v1PhysP1_T0Mon_build.py locally fails: Test trigP1_v1PhysP1_T0Mon_build finished with code 65 because the following required steps failed: ['Reco_tf.Tier0Reco', 'CheckLog’], and in particular failing in DQHistogramMerge for reasons not correlated with this MR
• run on 7 truncated events in the debug stream, and checked that errors on the flagged collections disappeared: athenaHLT.py -o output --file=/eos/atlas/atlastier0/rucio/data24_13p6TeV/debug_TruncatedHLTResult/00475192/data24_13p6TeV.00475192.debug_TruncatedHLTResult.daq.RAW/data24_13p6TeV.00475192.debug_TruncatedHLTResult.daq.RAW._lb0388._SFO-12._0001.data --file=/eos/atlas/atlastier0/rucio/data24_13p6TeV/debug_TruncatedHLTResult/00475192/data24_13p6TeV.00475192.debug_TruncatedHLTResult.daq.RAW/data24_13p6TeV.00475192.debug_TruncatedHLTResult.daq.RAW._lb0428._SFO-13._0001.data --file=/eos/atlas/atlastier0/rucio/data24_13p6TeV/debug_TruncatedHLTResult/00475192/data24_13p6TeV.00475192.debug_TruncatedHLTResult.daq.RAW/data24_13p6TeV.00475192.debug_TruncatedHLTResult.daq.RAW._lb0435._SFO-12._0001.data --file=/eos/atlas/atlastier0/rucio/data24_13p6TeV/debug_TruncatedHLTResult/00475192/data24_13p6TeV.00475192.debug_TruncatedHLTResult.daq.RAW/data24_13p6TeV.00475192.debug_TruncatedHLTResult.daq.RAW._lb0777._SFO-15._0001.data --file=/eos/atlas/atlastier0/rucio/data24_13p6TeV/debug_TruncatedHLTResult/00475192/data24_13p6TeV.00475192.debug_TruncatedHLTResult.daq.RAW/data24_13p6TeV.00475192.debug_TruncatedHLTResult.daq.RAW._lb0777._SFO-20._0001.data --file=/eos/atlas/atlastier0/rucio/data24_13p6TeV/debug_TruncatedHLTResult/00475192/data24_13p6TeV.00475192.debug_TruncatedHLTResult.daq.RAW/data24_13p6TeV.00475192.debug_TruncatedHLTResult.daq.RAW._lb0780._SFO-16._0001.data --file=/eos/atlas/atlastier0/rucio/data24_13p6TeV/debug_TruncatedHLTResult/00475192/data24_13p6TeV.00475192.debug_TruncatedHLTResult.daq.RAW/data24_13p6TeV.00475192.debug_TruncatedHLTResult.daq.RAW._lb0898._SFO-14._0001.data --file=/eos/atlas/atlastier0/rucio/data24_13p6TeV/debug_TruncatedHLTResult/00475192/data24_13p6TeV.00475192.debug_TruncatedHLTResult.daq.RAW/data24_13p6TeV.00475192.debug_TruncatedHLTResult.daq.RAW._lb0898._SFO-19._0001.data TriggerJobOpts.runHLT Trigger.triggerMenuSetup="PhysicsP1_pp_run3_v1_HLTReprocessing_prescale" Trigger.doLVL1=True >athenaHLT.log 2>&1

I added more info in the ERROR to identify the first collection that got oversized. Indeed even with the TrucantionAllowed on 2 collections, some errors are raised for other collections going oversize before them in the list of the EDM file, but the message was indicating only the largest collections. The current message tells which is the collections that caused the oversize (the first one dropped) for each moduleId.