Need 'Authoritative Identifier' so an import from AlphaFill 3D-beacons yields multiple 'Cached PDB' files

The alphafill.eu service provides alphafold models 'enriched' with ligand structures. Importing from this with the 2.11.2 development version works, but when the 3d-structure chooser is opened after viewing the structure, two entries are shown for the file imported from Alphafill - one with the Alphafill DB identifier, one looking like an AlphaFold identifier (AF-Uniprot-F1).

Cause: The mmcif file provided via the 3D-beacons api includes the original alphafold database identifier, which confuses the PDBEntry.updateFrom logic which assumes the identifier embedded in the file is meaningful.