fix: pin advancemame at AmberELEC's build

The three builds the platforms ship are 5f301c8 (Recalbox), 6a34ec0
(EmuELEC) and 0f6a767 (AmberELEC): 5f301c8 is an ancestor of 6a34ec0,
itself an ancestor of 0f6a767. 0f6a767 is no longer on the rewritten
branch and is fetched by its sha. The profile was held at 799060b,
which none of them builds, so EveryBuildReferenceNamesThePin failed.

At 0f6a767 and its two ancestors the same 26 BIOS roots are registered
with the same contents. aleck64, atarisy1, cedmag and coh1002v are not
among them and leave the profile with the Aleck64 and Cedar Magnet
systems, and hng64 (src/drivers/hng64.c:1425-1431, 1718) joins it.
Every ref is moved with the pin and read again. Each cited line holds
the same text at 6a34ec0 and 5f301c8, except advance/osd/video.c:1787,
1795: Recalbox's 5f301c8 compiles those tables from blitmax.h and
startup.h, now said in the notes. The doc/advmame.d citations, worded
otherwise in the older builds, give way to the code that does it
(advance/linux/file.c:87-99, src/romload.c:167-204), and the artwork
refs to src/artwork.c, the loader of this revision.

Manifests: AmberELEC and Recalbox gain hng64.zip and lose aleck64.zip,
cedmag.zip and coh1002v.zip at their BIOS root. EmuELEC loses
cedmag.zip from arcade and mame, its other three stay for MAME 2010
and 2003-Plus, and hng64.zip takes the copy holding the advancemame
members. profile_sync: 0 to review, config_reads BUILD_OK at 6a34ec0.

tests/test_profile_sync.py

@@ -3077,11 +3077,13 @@ class TestDeliberatelyFrozenPin(TestBuildReport):
         # live build can add a system its frozen revision lacked
         # (advancemame's coh1002v, after advmame-1.4), so the frozen one's
         # systems are a subset, not an equal set. A live build can also drop
-        # a system upstream deleted: advancemame removed its Hyper Neo Geo 64
-        # driver in dff25b6ee7, which advmame-1.4 still carries.
+        # a system upstream deleted: AdvanceMAME removed its Hyper Neo Geo 64
+        # driver in dff25b6ee7, which advmame-1.4 and advancemame (AmberELEC's
+        # 0f6a767) still carry.
         removed_upstream = {
             ("advmame-1.4", "advancemame"): {"hyper-neogeo64"},
             ("advmame-1.4", "advmame"): {"hyper-neogeo64"},
+            ("advancemame", "advmame"): {"hyper-neogeo64"},
         }
         pairs = 0
         for names in by_source.values():