[NPM-3662] Add sestatus to agent flare

[pimlu]

What does this PR do?

This probe writes the output of sestatus to system-probe/selinux_sestatus.log.

This PR is a rebase of #31088 on top of Bryce's SystemProbeUtil refactors.

Motivation

Various distros ship selinux by default and this is useful for support on customers deploying selinux.

Describe how you validated your changes

Run a flare and check system-probe/selinux_sestatus.log

Possible Drawbacks / Trade-offs

Additional Notes

[cit-pr-commenter]

Go Package Import Differences

Baseline: 367c4b6
Comparison: 6aea6fc

binary	os	arch	change
system-probe	linux	amd64	+1, -0 +github.com/DataDog/datadog-agent/cmd/system-probe/api/debug
system-probe	linux	arm64	+1, -0 +github.com/DataDog/datadog-agent/cmd/system-probe/api/debug
system-probe	windows	amd64	+1, -0 +github.com/DataDog/datadog-agent/cmd/system-probe/api/debug

[pimlu]

Will need to fix those integration tests

[agent-platform-auto-pr]

Test changes on VM

Use this command from test-infra-definitions to manually test this PR changes on a VM:

inv aws.create-vm --pipeline-id=50902898 --os-family=ubuntu

Note: This applies to commit 6aea6fc

[agent-platform-auto-pr]

Package size comparison

Comparison with ancestor 367c4b6154a709751eac1c92b7d0b0957aa83511

Diff per package

package	diff	status	size	ancestor	threshold
datadog-agent-amd64-deb	0.01MB	⚠️	1265.84MB	1265.83MB	140.00MB
datadog-iot-agent-amd64-deb	0.00MB	⚠️	113.27MB	113.26MB	10.00MB
datadog-dogstatsd-amd64-deb	0.00MB	✅	78.41MB	78.41MB	10.00MB
datadog-heroku-agent-amd64-deb	0.00MB	✅	526.60MB	526.60MB	70.00MB
datadog-agent-x86_64-rpm	0.01MB	⚠️	1275.07MB	1275.06MB	140.00MB
datadog-agent-x86_64-suse	0.01MB	⚠️	1275.07MB	1275.06MB	140.00MB
datadog-iot-agent-x86_64-rpm	0.00MB	⚠️	113.34MB	113.33MB	10.00MB
datadog-iot-agent-x86_64-suse	0.00MB	⚠️	113.34MB	113.33MB	10.00MB
datadog-dogstatsd-x86_64-rpm	0.00MB	✅	78.49MB	78.49MB	10.00MB
datadog-dogstatsd-x86_64-suse	0.00MB	✅	78.49MB	78.49MB	10.00MB
datadog-agent-arm64-deb	0.00MB	✅	1000.83MB	1000.83MB	140.00MB
datadog-iot-agent-arm64-deb	0.00MB	✅	108.75MB	108.75MB	10.00MB
datadog-dogstatsd-arm64-deb	0.00MB	✅	55.64MB	55.64MB	10.00MB
datadog-agent-aarch64-rpm	0.00MB	⚠️	1010.04MB	1010.04MB	140.00MB
datadog-iot-agent-aarch64-rpm	0.00MB	⚠️	108.82MB	108.82MB	10.00MB

Decision

⚠️ Warning

[cit-pr-commenter]

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: dc2ddae2-95d8-4bae-a95c-05473c270ea3

Baseline: 367c4b6
Comparison: 6aea6fc
Diff

Optimization Goals: ✅ No significant changes detected

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	quality_gate_idle_all_features	memory utilization	+1.48	[+1.35, +1.60]	1	Logs bounds checks dashboard
➖	tcp_syslog_to_blackhole	ingress throughput	+0.79	[+0.72, +0.86]	1	Logs
➖	quality_gate_logs	% cpu utilization	+0.66	[-2.29, +3.61]	1	Logs
➖	file_to_blackhole_1000ms_latency	egress throughput	+0.25	[-0.54, +1.04]	1	Logs
➖	quality_gate_idle	memory utilization	+0.16	[+0.11, +0.21]	1	Logs bounds checks dashboard
➖	file_to_blackhole_0ms_latency_http1	egress throughput	+0.04	[-0.85, +0.93]	1	Logs
➖	file_to_blackhole_1000ms_latency_linear_load	egress throughput	+0.04	[-0.43, +0.51]	1	Logs
➖	file_to_blackhole_500ms_latency	egress throughput	+0.01	[-0.76, +0.78]	1	Logs
➖	uds_dogstatsd_to_api	ingress throughput	+0.01	[-0.08, +0.10]	1	Logs
➖	tcp_dd_logs_filter_exclude	ingress throughput	+0.00	[-0.01, +0.01]	1	Logs
➖	uds_dogstatsd_to_api_cpu	% cpu utilization	-0.01	[-0.74, +0.71]	1	Logs
➖	file_to_blackhole_300ms_latency	egress throughput	-0.02	[-0.65, +0.61]	1	Logs
➖	file_to_blackhole_0ms_latency_http2	egress throughput	-0.03	[-0.86, +0.80]	1	Logs
➖	file_to_blackhole_100ms_latency	egress throughput	-0.04	[-0.76, +0.67]	1	Logs
➖	file_to_blackhole_0ms_latency	egress throughput	-0.14	[-0.97, +0.70]	1	Logs
➖	file_tree	memory utilization	-0.19	[-0.31, -0.06]	1	Logs
➖	otel_to_otel_logs	ingress throughput	-0.30	[-0.97, +0.37]	1	Logs

Bounds Checks: ✅ Passed

perf	experiment	bounds_check_name	replicates_passed	links
✅	file_to_blackhole_0ms_latency	lost_bytes	10/10
✅	file_to_blackhole_0ms_latency	memory_usage	10/10
✅	file_to_blackhole_0ms_latency_http1	lost_bytes	10/10
✅	file_to_blackhole_0ms_latency_http1	memory_usage	10/10
✅	file_to_blackhole_0ms_latency_http2	lost_bytes	10/10
✅	file_to_blackhole_0ms_latency_http2	memory_usage	10/10
✅	file_to_blackhole_1000ms_latency	memory_usage	10/10
✅	file_to_blackhole_1000ms_latency_linear_load	memory_usage	10/10
✅	file_to_blackhole_100ms_latency	lost_bytes	10/10
✅	file_to_blackhole_100ms_latency	memory_usage	10/10
✅	file_to_blackhole_300ms_latency	lost_bytes	10/10
✅	file_to_blackhole_300ms_latency	memory_usage	10/10
✅	file_to_blackhole_500ms_latency	lost_bytes	10/10
✅	file_to_blackhole_500ms_latency	memory_usage	10/10
✅	quality_gate_idle	memory_usage	10/10	bounds checks dashboard
✅	quality_gate_idle_all_features	memory_usage	10/10	bounds checks dashboard
✅	quality_gate_logs	lost_bytes	10/10
✅	quality_gate_logs	memory_usage	10/10

Explanation

Confidence level: 90.00%
Effect size tolerance: |Δ mean %| ≥ 5.00%

Performance changes are noted in the perf column of each table:

• ✅ = significantly better comparison variant performance
• ❌ = significantly worse comparison variant performance
• ➖ = no significant change in performance

A regression test is an A/B test of target performance in a repeatable rig, where "performance" is measured as "comparison variant minus baseline variant" for an optimization goal (e.g., ingress throughput). Due to intrinsic variability in measuring that goal, we can only estimate its mean value for each experiment; we report uncertainty in that value as a 90.00% confidence interval denoted "Δ mean % CI".

For each experiment, we decide whether a change in performance is a "regression" -- a change worth investigating further -- if all of the following criteria are true:

1. Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.

2. Its 90.00% confidence interval "Δ mean % CI" does not contain zero, indicating that if our statistical model is accurate, there is at least a 90.00% chance there is a difference in performance between baseline and comparison variants.

3. Its configuration does not mark it "erratic".

CI Pass/Fail Decision

✅ Passed. All Quality Gates passed.

• quality_gate_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_idle_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.