R & V+ never needed this as there is no platform
loading of mainline bpf.
On T/U we've been loading via mainline NetBpfLoad
for the past year, so the struct sizes only actually
matter for S.
S switches to mainline NetBpfLoad in M-2025-05
(currently in small canary), at which point the
struct sizes stop mattering.
In M-2025-07 S/T/U still look at the 'min bpf loader'
section of the .o, but don't go any deeper.
In M-2025-08 we no longer ship any bpf .o
files that need to be parsed by platform
bpfloader (as they're in a different subdirectory
in the tethering apex they don't even look in).
Test: TreeHugger
Flag: EXEMPT test deletion
Signed-off-by: Maciej Żenczykowski <maze@google.com>
Change-Id: I72b9ebcf4ea59e61cdfd8bb009ede13670e3421f
e8cba91fd5