Fixes for MiniAODv4

This fixes issues related to global tags, photons (#186), and triggers (#178 (closed)) in Run 3. I could ntuplise one of the CAT test MiniAOD files with the following config:

{
    "preseed": 1743706825,
    "git": {
        "commit": "41bc9d0df003318",
        "repo": "/home/louis/Documents/Darwin/Installer/Darwin",
        "reproducible": false,
        "complete": false
    },
    "software": {
        "Boost": "1_85",
        "Cpp": "C++20",
        "Darwin": "41bc9d0df003318ffbf0ac0f2250bf53fad5ec32",
        "ROOT": "6.30/04",
        "gpp": "12.3.0",
        "libgit2": "1.8.1"
    },
    "flags": {
        "isMC": true,
        "R": 4,
        "options": [
            "muons",
            "flavour-disabled",
            "jets",
            "photons",
            "triggers"
        ],
        "year": 2023,
        "labels": [
            "BPix",
            "PUPPI"
        ]
    }
}

Note that flavour (#188) is still not supported. However, photons and triggers now work.

The photon objects required the addition of two new variables to guarantee that the scale and smearing corrections (provided in correctionlib for Run 3) could be applied.

This MR overlaps with !234 (merged), but switches back to PAT in all cases. My investigation in #178 (closed) indeed indicates that data files also use PAT for trigger objects. I'm not sure where the RECO initially came from.

I'm using labels to communicate the sub-era to the Ntupliser config, leaving a more thorough review of the layout to https://gitlab.cern.ch/groups/cms-analysis/general/DasAnalysisSystem/-/milestones/4. In particular I would find it more practical if the year field has space for an era label: "year": [2023, "BPix"], "year": [2022, "RunC"].