Guard TrigEDMConfig import unless looking at bytestream files
In order to use the TrigDecisionToolCfg function in AthAnalysis we need to include the TriggerJobOpts package in the release to access the TriggerJobOpts.TriggerConfigFlags module. This module then has a dependency on TrigEDMConfig which then results in a dependency cascade.
This dependency is only used when looking at bytestream files which I doubt is possible in AthAnalysis anyway so I've guarded that import statement inside the relevant if block.
In adding the TriggerJobOpts package to AthAnalysis we do get a few modules which cannot be imported as they depend on other imports which we cannot include without a dependency cascade - I'm not sure if this is acceptable or not.
@cjmeyer - can you check if you can run your code in AthAnalysis with this fix?
Closes ATR-25066