Update bcc to add subpackage libbpf-tools

[rlmenge]

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

• The toolchain has been rebuilt successfully (or no changes were made to it)
• The toolchain/worker package manifests are up-to-date
• Any updated packages successfully build (or no packages were changed)
• Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
• Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
• All package sources are available
• cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
• LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
• All source files have up-to-date hashes in the *.signatures.json files
• sudo make go-tidy-all and sudo make go-test-coverage pass
• Documentation has been updated to match any changes to the build system
• Ready to merge

---

Summary

Add new subpackage libbpf-tools to the bcc package. Resulting binaries are placed in /usr/sbin/bpf-* and contain "bpf" as a prefix similar to other distros (Fedora, Alpine Linux)

There is a way to add the prefix at compile time but it is in versions [v0.30.0](https://github.com/iovisor/bcc/releases/tag/v0.30.0) iovisor/bcc@3469bf1

Related LISA test: microsoft/lisa#4161
Related Bug: https://microsoft.visualstudio.com/OS/_workitems/edit/60562791/

Change Log

• Add libbpf-tools to bcc

Does this affect the toolchain?

NO

Test Methodology

• https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1001920&view=results
• tested local build + install and was able to run binaries

$ sudo /usr/sbin/bpf-execsnoop
PCOMM            PID    PPID   RET ARGS
sh               1007071 698      0 /bin/sh -c -- ip route show dev eth0 | awk '/default/ {print $3 }' 
ip               1007072 1007071   0 /usr/sbin/ip route show dev eth0 
awk              1007073 1007071   0 /usr/bin/awk /default/ {print $3 } 
sh               1007074 698      0 /bin/sh -c -- ip -f inet6  route show dev eth0 | awk '/default/ {print $3 }' 
ip               1007075 1007074   0 /usr/sbin/ip -f inet6 route show dev eth0 
awk              1007076 1007074   0 /usr/bin/awk /default/ {print $3 } 
sh               1007077 698      0 /bin/sh -c -- /usr/libexec/hypervkvpd/hv_get_dns_info 
hv_get_dns_info  1007077 698      0 /usr/libexec/hypervkvpd/hv_get_dns_info 
cat              1007078 1007077   0 /usr/bin/cat /etc/resolv.conf 
awk              1007079 1007077   0 /usr/bin/awk /^nameserver/ { print $2 }
^C
$ sudo /usr/sbin/bpf-biolatency
Tracing block device I/O... Hit Ctrl-C to end.
^C

     usecs               : count    distribution
         0 -> 1          : 0        |                                        |
         2 -> 3          : 0        |                                        |
         4 -> 7          : 0        |                                        |
         8 -> 15         : 0        |                                        |
        16 -> 31         : 0        |                                        |
        32 -> 63         : 0        |                                        |
        64 -> 127        : 0        |                                        |
       128 -> 255        : 0        |                                        |
       256 -> 511        : 0        |                                        |
       512 -> 1023       : 11       |*                                       |
      1024 -> 2047       : 258      |****************************************|
      2048 -> 4095       : 121      |******************                      |

[rlmenge]

Github check failures related to ptests for python-requests and python-responses are expected.