As I understand it, accessing and setting read only global variables from a userspace control program through libbpf can only happen when importing a BPF skeleton. Things like `bpf_object__find_map_by_name()` are exposed but the name of this map is internal and `internal_map_name()` is as well. Traversing through the maps array via bpf_object directly doesn't seem possible either. Why is this feature only available through generating a skeleton? Should there be differences in supported functionality between using a skeleton and using libbpf directly?
