fix: BPF_PROG_TYPE issue for android

[pomhg]

Background

pname is useful for dae running on android, e.g. pname(netd) -> must_direct. (netd is the networkmanager for android)
dae pname not working on android, coz the bpf prog type name is different in libbpf_android.

Error 1
FATA[0002] Attach(group: (GroupSock(tproxy_wan_cg_sock_create)#27: create link: operation not permitted

Error 2
FATA[0000] load eBPF objects: field TproxyWanCgConnect4: cannot load program tproxy_wan_cg_connect4: program type is unspecified

Refs.
AOSP Extending the Kernel with eBPF

Loader.cpp main branch source

Loader.cpp android13-qpr3-release branch source

Checklist

• The Pull Request has been fully tested
• There's an entry in the CHANGELOGS
• There is a user-facing docs PR against https://github.com/daeuniverse/dae

Full Changelogs

• Error 1 solved
• Error 2 upstream AOSP newer version of bpfloader for android needed, coz connect4/6 and sendmsg4/6 are not fully supported until bpfloader v0.36 which is now v0.19 in android13-qpr3-release branch.

Issue Reference

Closes #[issue number]

Test Result