[WIP] Added ioctl kprobe to USM

[val06]

What does this PR do

Added erpc handler to communicate with dd-java-agent capturing the TLS traffic from Java applications

Motivation

we capture TLS traffic in java applications using our dd-java-agent who in turn sends the captured data via a ioctl with special request code. SystemProbe should capture the data by setting a kprobe on the ioctl handler

Additional Notes

Should be synced with this PR

Describe how to test/QA your changes

full e2e test should test injection of dd-java-agent and getting the tls traffic in systemprobe as part of the CI.

Reviewer's Checklist

• If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
• Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
• A release note has been added or the changelog/no-changelog label has been applied.
• Changed code has automated tests for its functionality.
• Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
• At least one team/.. label has been applied, indicating the team(s) that should QA this change.
• If applicable, docs team has been notified or an issue has been opened on the documentation repo.
• If applicable, the need-change/operator and need-change/helm labels have been applied.
• If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
• If applicable, the config template has been updated.