Update golang.org/x deps

[pgimalac]

What does this PR do?

Update all golang.org/x/... dependencies.

Motivation

Keep dependencies up to date and close a dozen dependabot PRs.

Update go golang.org/x/crypto to 0.31.0 fixes CVE-2024-45337.

Describe how you validated your changes

Handled by CI.

Possible Drawbacks / Trade-offs

Additional Notes

I should make a scheduled github workflow to open this PR as it becomes annoying.

[agent-platform-auto-pr]

Package size comparison

Comparison with ancestor 22edfebf2aa1cc44aceff9da5b46f2fb185a5a53

Diff per package

package	diff	status	size	ancestor	threshold
datadog-agent-amd64-deb	0.02MB	⚠️	1266.01MB	1265.99MB	140.00MB
datadog-iot-agent-amd64-deb	0.01MB	⚠️	113.27MB	113.27MB	10.00MB
datadog-dogstatsd-amd64-deb	0.01MB	⚠️	78.51MB	78.50MB	10.00MB
datadog-heroku-agent-amd64-deb	0.02MB	⚠️	526.75MB	526.73MB	70.00MB
datadog-agent-x86_64-rpm	0.02MB	⚠️	1275.25MB	1275.22MB	140.00MB
datadog-agent-x86_64-suse	0.02MB	⚠️	1275.25MB	1275.22MB	140.00MB
datadog-iot-agent-x86_64-rpm	0.01MB	⚠️	113.34MB	113.34MB	10.00MB
datadog-iot-agent-x86_64-suse	0.01MB	⚠️	113.34MB	113.33MB	10.00MB
datadog-dogstatsd-x86_64-rpm	0.00MB	⚠️	78.59MB	78.58MB	10.00MB
datadog-dogstatsd-x86_64-suse	0.00MB	⚠️	78.59MB	78.58MB	10.00MB
datadog-agent-arm64-deb	0.02MB	⚠️	1001.01MB	1000.98MB	140.00MB
datadog-iot-agent-arm64-deb	0.01MB	⚠️	108.76MB	108.75MB	10.00MB
datadog-dogstatsd-arm64-deb	0.00MB	⚠️	55.73MB	55.73MB	10.00MB
datadog-agent-aarch64-rpm	0.02MB	⚠️	1010.22MB	1010.20MB	140.00MB
datadog-iot-agent-aarch64-rpm	0.01MB	⚠️	108.83MB	108.82MB	10.00MB

Decision

⚠️ Warning

[cit-pr-commenter]

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: 395b2109-7325-4059-8ae6-d43369f58cec

Baseline: 22edfeb
Comparison: bfdfcda
Diff

Optimization Goals: ✅ No significant changes detected

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	uds_dogstatsd_to_api_cpu	% cpu utilization	+1.07	[+0.34, +1.80]	1	Logs
➖	file_tree	memory utilization	+0.75	[+0.63, +0.87]	1	Logs
➖	tcp_syslog_to_blackhole	ingress throughput	+0.32	[+0.25, +0.39]	1	Logs
➖	otel_to_otel_logs	ingress throughput	+0.29	[-0.37, +0.95]	1	Logs
➖	quality_gate_idle_all_features	memory utilization	+0.20	[+0.08, +0.33]	1	Logs bounds checks dashboard
➖	file_to_blackhole_300ms_latency	egress throughput	+0.16	[-0.47, +0.79]	1	Logs
➖	file_to_blackhole_0ms_latency_http2	egress throughput	+0.16	[-0.72, +1.04]	1	Logs
➖	file_to_blackhole_0ms_latency_http1	egress throughput	+0.02	[-0.87, +0.92]	1	Logs
➖	file_to_blackhole_100ms_latency	egress throughput	+0.02	[-0.66, +0.70]	1	Logs
➖	tcp_dd_logs_filter_exclude	ingress throughput	-0.00	[-0.01, +0.01]	1	Logs
➖	file_to_blackhole_0ms_latency	egress throughput	-0.00	[-0.79, +0.79]	1	Logs
➖	uds_dogstatsd_to_api	ingress throughput	-0.01	[-0.12, +0.09]	1	Logs
➖	file_to_blackhole_1000ms_latency_linear_load	egress throughput	-0.09	[-0.54, +0.36]	1	Logs
➖	quality_gate_logs	% cpu utilization	-0.19	[-3.12, +2.74]	1	Logs
➖	quality_gate_idle	memory utilization	-0.20	[-0.24, -0.15]	1	Logs bounds checks dashboard
➖	file_to_blackhole_500ms_latency	egress throughput	-0.33	[-1.10, +0.44]	1	Logs
➖	file_to_blackhole_1000ms_latency	egress throughput	-0.35	[-1.13, +0.43]	1	Logs

Bounds Checks: ❌ Failed

perf	experiment	bounds_check_name	replicates_passed	links
❌	file_to_blackhole_0ms_latency_http2	lost_bytes	9/10
❌	file_to_blackhole_100ms_latency	lost_bytes	9/10
✅	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	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	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_idle_all_features, bounds check memory_usage: 10/10 replicas passed. Gate 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.

[davidor]

👍 for container-platform files

[pgimalac]

/merge

[dd-devflow]

Devflow running: /merge

View all feedbacks in Devflow UI.

---

2024-12-12 15:55:31 UTC ℹ️ MergeQueue: pull request added to the queue

The median merge time in main is 26m.

---

2024-12-12 16:34:34 UTC ℹ️ MergeQueue: This merge request was merged