Refactor children_fru_keys into separate arrays
To implement the sanity check in cl/744092037, we must remove any objects from the FruTable that will not be traversed in the topology and are not real scanned Frus.
It is inaccurate to consider Processors and Storage as Fru objects since these are not detected by Fru scanning today. We keep their Id as an array in the associated Fru object. We will use this to construct the link to the object.
As part of this refactor, we separate the children_fru_keys by distinct resource types, the Fru proto will keep a separate array for each type.
#tlbmc
PiperOrigin-RevId: 744892988
Change-Id: Ic1c415dc5e8a01a33d7bde90832701ba5dd5a69e
diff --git a/gbmcweb b/gbmcweb
index b2de88d..24d1b58 160000
--- a/gbmcweb
+++ b/gbmcweb
@@ -1 +1 @@
-Subproject commit b2de88d6a622d7c0c3bdd80bf628ecd1a2d54746
+Subproject commit 24d1b58baf45a1f01a4bb734c9f999276f2d78b1
