[thiagoftsm]

Summary

Sync current branch with netdata/libbpf;

Test Plan

1. Get binaries according to your C library from [this](ADD ACTIONS LINK HERE) link and extract them inside a directory, for example: ../artifacts.
   You can also get everything for glibc [here](UPLOAD FILE WITH ALL BINARIES TO SIMPLIFY REVIEWERS).

2. Extract them running:

   $ for i in `ls *.zip`; do unzip $i; rm .gitkeep ; rm $i; done
   $ for i in `ls *.tar`; do tar -xf $i; rm $i* ; done

3. Compile branch an run the following tests:

   # /tests/legacy_test --netdata-path ../artifacts/ --pid 2 --common --iteration 1 --disk --ext4 2> err_probe_c >out_probe_c; ./tests/legacy_test --netdata-path ../artifacts/ --pid 2 --common --iteration 1 --disk --ext4 2> err_probe_c >out_probe_c

4. Every test should ends with Success, unless you do not have a specific target (function) available.

Additional information

This PR was tested on:

Linux Distribution	Environment	Kernel Version
Slackware Linux	Bare metal	7.2.8
Debian 13	VM	6.12.107+deb13
Alma 9	VM	5.14.8-687.54.1.el9_8
Alma 8	VM	4.18.0-553.164

[stelfrag]

Tested on Debian 13 (6.12.107, SCSI disk) with this PR's CI glibc artifacts:

• C and Go testers build clean against the new libbpf; go vet / go test pass.
• Test plan (--pid 2 --common --disk --ext4): 42/42 Success, valid JSON. Disk now selects disk.6.8 and records latency for sda (master's tester picked disk.5.4 and failed).
• --arena 18/18, --buffer --pid 3 18/18, --all 44 Success (the 10 failures are btrfs/mdflush/nfs/xfs/zfs, not present on the host).
• Release consolidation: no filename collisions across the glibc artifacts.

Follow-ups:

• netdata/netdata needs a matching change before users see the disk fix: the disk module's kernel mask (ebpf.c) stops at 5.4/5.14, and neither plugin knows the 5.17 / 7.0 suffixes (libbpf_api/ebpf.c, ebpfgo loader.go).
• The test plan should include --content; without it control tables are not filled and every ring buffer reads 0 samples.
• .dockerfiles/change_libbpf.sh is now unused, but kernel/DEVELOPER.md still documents it.