[FEATURE] Add CI to test bpftrace

[tdaudi]

Description

This PR is base on the requested feature to add bpftrace GitHub actions.

Fixes # (issue) : github.com//issues/228

Type of change

• New feature (non-breaking change which adds functionality)

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• I have checked my code and corrected any misspellings

[tdaudi]

Several problems remain with the draft.

• I use apt install bpftrace to install bpftrace. Problem is, on ubuntu the package is not up-to-date. So next step will be to clone bpftrace and install it. But the downside will be the image will be incredibly heavy, and this test will take ages to perform ...
• I need to fix the error [error] [agent.cpp:105] Unable to initialize shared memory: No such file or directory when using the script inside Docker. I still don't know why this happened

[tdaudi]

If you want to work on this later on, you have to notice two things :

• To test bpftrace you would like to build bpftrace from source inside the GitHub action to use the latest version, which is not trivial and may slow down a lot the running task.
• GitHub does not yet have Ubuntu 24 available for actions, so if you want to use the built-in package, you have to test bpftime on an older kernel or old bpftrace package. If breaking change occurs, you won't know

[yunwei37]

Thanks @ScriptSathi!

[yunwei37]

This draft is stale and conflicts with master; its own notes still leave the bpftrace version/source-build strategy unresolved. If it is to continue, please rebase and choose a pinned bpftrace revision plus a cacheable build/test path with an explicit runtime budget. Without that reproducible plan there is no safe CI patch to apply.