Break out trigger content into a separate module and customise trigger b-tag content by year

Precursor to any further improvements of the trigger content toggles in the Derivation Framework code -- extract the code handling all trigger output content into a DerivationFrameworkTrigger module. For simplicity and transparency, explicit trigger collection names have changed to HLT_[Signature]TriggerContent as smart slimming keys.

The logic deciding which branches to store is moved into the [Signature]TriggerContent modules, via a function dependent on the configFlags, rather than having separate names for Run 2 and Run 3. The Run 3 b-jet trigger content is customised to contain only the primary b-tagging probabilities for each year of Run 3.

I could not find any clear documentation for the JetTriggerFixContent or EtMissTriggerFixContent, as their additions predate the git migration, so have simply merged those into JetTriggerContent and EtMissTriggerContent respectively, eliminating those files.

FYI @lshi @boliu

TODO:

• Move run/year logic into smart slimming files
• Simplify names for content additions, rather than using HLT container names
• Move all trigger content lists from DerivationFrameworkCore to DerivationFrameworkTrigger