[Backport 7.82.x] Bump Bazel to 9.2.0 for remote cache and Windows fixes (#53619)

[alopezz]

Bump the pinned Bazel version from 9.1.1 to 9.2.0 and refresh MODULE.bazel.lock accordingly.

Bazel 9.2.0 ships fixes this repo has been working around over the past month.

Our contributions:

• [9.2.0] Fix launching executables whose path can't be shortened on Windows (https://github.com/bazelbuild/bazel/pull/29921) bazelbuild/bazel#29984, which should remove the need for temporary countermeasures we had to come up with:

  • [#incident-56436] Enable NTFS 8.3 short names in the Windows image datadog-agent-buildimages#1212 (alas ineffective),
  • [#incident-56436] Enable NTFS 8.3 short names at startup datadog-agent-buildimages#1215 (effective),
  • Fail bazel.bat early if 8.3 short names are disabled in Windows #52500,

• [9.2.0] Reland "Embed asInvoker UAC manifest in the Windows launcher stub" (https://github.com/bazelbuild/bazel/pull/30043) bazelbuild/bazel#30182, which should remove the need for:

  • Fix bazel run *install* for non-admin Windows users #52061,
  • chore(bazel): add --test_env=__COMPAT_LAYER=RunAsInvoker for Windows bazel test #53591.

• [9.2.0] Cache CAS interactions at lower layer to fix lost input handl… bazelbuild/bazel#29791,

• [9.2.0] Reupload in-memory blobs when inputs are force uploaded (https://github.com/bazelbuild/bazel/pull/29831) bazelbuild/bazel#29868,

• [9.2.0] Remove the client gRPC message size limit (https://github.com/bazelbu… bazelbuild/bazel#29885,

• [9.2.0] Recover lost inputs from deduplicated Merkle subtrees under path mapping bazelbuild/bazel#30193, a caveat mentioned in:

  • Enable Bazel action rewinding for Lost inputs no longer available remotely #53356.

Also worth noting, though not tied to a specific incident here:

• [9.2.0] Ensure that transitive packages can be flattened efficiently (https://github.com/bazelbuild/bazel/pull/29800) bazelbuild/bazel#29807,
• [9.2.0] Enable TCP keepalive by default for gRPC connections. (https://github.com/bazelbuild/bazel/pull/29879) bazelbuild/bazel#29898,
• [9.2.0] Inject the repo env per-variable to avoid over-invalidation bazelbuild/bazel#30194.

bazel version reports 9.2.0 after bazelisk re-bootstraps. bazel build //pkg/config/schema/... completes successfully. bazel shutdown followed by bazel mod deps --lockfile_mode=refresh leaves MODULE.bazel.lock unchanged.

None of the .bazelrc UAC/8dot3 workarounds (DataDog/datadog-agent-buildimages#1215, #52500, #52061, #53591) are removed here. Each needs its own re-verification on Windows before being reverted as follow-ups.

(cherry picked from commit 695123c)

What does this PR do?

Motivation

Describe how you validated your changes

Additional Notes

[temporal-github-worker-1]

Backport evaluation: View Slack thread

[dd-octo-sts]

Files inventory check summary

File checks results against ancestor c1119389:

Results for datadog-agent_7.82.2.git.4.2d570ab.pipeline.132351110-1_amd64.deb:

No change detected

[cit-pr-commenter-54b7da]

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Job ID: 5e337159-de0e-4ac0-8da1-314327526d7e

Baseline: c111938
Comparison: 2d570ab
Diff

Optimization Goals: ✅ No significant changes detected

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	quality_gate_metrics_logs	memory utilization	+1.13	[+0.88, +1.38]	1	Logs bounds checks dashboard
➖	quality_gate_logs	% cpu utilization	+0.32	[-0.66, +1.30]	1	Logs bounds checks dashboard
➖	quality_gate_idle	memory utilization	+0.06	[+0.00, +0.11]	1	Logs bounds checks dashboard
➖	quality_gate_security_mean_fs_load	memory utilization	+0.01	[-0.03, +0.05]	1	Logs bounds checks dashboard
➖	quality_gate_security_no_fs_load	memory utilization	+0.01	[-0.09, +0.10]	1	Logs bounds checks dashboard
➖	quality_gate_security_idle	memory utilization	-0.15	[-0.21, -0.08]	1	Logs bounds checks dashboard
➖	quality_gate_idle_all_features	memory utilization	-0.38	[-0.42, -0.34]	1	Logs bounds checks dashboard

Bounds Checks: ✅ Passed

perf	experiment	bounds_check_name	replicates_passed	observed_value	links
✅	quality_gate_idle	intake_connections	10/10	3 ≤ 4	bounds checks dashboard
✅	quality_gate_idle	memory_usage	10/10	148.00MiB ≤ 154MiB	bounds checks dashboard
✅	quality_gate_idle	total_bytes_received	10/10	741.77KiB ≤ 819.20KiB	bounds checks dashboard
✅	quality_gate_idle_all_features	intake_connections	10/10	3 ≤ 4	bounds checks dashboard
✅	quality_gate_idle_all_features	memory_usage	10/10	491.68MiB ≤ 495MiB	bounds checks dashboard
✅	quality_gate_idle_all_features	total_bytes_received	10/10	1.13MiB ≤ 1.25MiB	bounds checks dashboard
✅	quality_gate_logs	intake_connections	10/10	3 ≤ 6	bounds checks dashboard
✅	quality_gate_logs	memory_usage	10/10	183.36MiB ≤ 195MiB	bounds checks dashboard
✅	quality_gate_logs	missed_bytes	10/10	0B = 0B	bounds checks dashboard
✅	quality_gate_logs	total_bytes_received	10/10	264.15MiB ≤ 292MiB	bounds checks dashboard
✅	quality_gate_metrics_logs	cpu_usage	10/10	347.70 ≤ 2000	bounds checks dashboard
✅	quality_gate_metrics_logs	intake_connections	10/10	3 ≤ 6	bounds checks dashboard
✅	quality_gate_metrics_logs	memory_usage	10/10	417.59MiB ≤ 430MiB	bounds checks dashboard
✅	quality_gate_metrics_logs	missed_bytes	10/10	0B = 0B	bounds checks dashboard
✅	quality_gate_metrics_logs	total_bytes_received	10/10	0.93GiB ≤ 1.04GiB	bounds checks dashboard
✅	quality_gate_security_idle	cpu_usage	10/10	27.64 ≤ 40	bounds checks dashboard
✅	quality_gate_security_idle	memory_usage	10/10	295.32MiB ≤ 330MiB	bounds checks dashboard
✅	quality_gate_security_mean_fs_load	cpu_usage	10/10	63.42 ≤ 80	bounds checks dashboard
✅	quality_gate_security_mean_fs_load	memory_usage	10/10	276.69MiB ≤ 310MiB	bounds checks dashboard
✅	quality_gate_security_no_fs_load	cpu_usage	10/10	22.38 ≤ 40	bounds checks dashboard
✅	quality_gate_security_no_fs_load	memory_usage	10/10	283.81MiB ≤ 320MiB	bounds checks dashboard

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_security_idle, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
• quality_gate_security_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check missed_bytes: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check total_bytes_received: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check total_bytes_received: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check missed_bytes: 10/10 replicas passed. Gate passed.
• quality_gate_security_no_fs_load, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_security_no_fs_load, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
• quality_gate_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_idle, bounds check total_bytes_received: 10/10 replicas passed. Gate passed.
• quality_gate_idle, bounds check intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_idle_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_idle_all_features, bounds check intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_idle_all_features, bounds check total_bytes_received: 10/10 replicas passed. Gate passed.
• quality_gate_security_mean_fs_load, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_security_mean_fs_load, bounds check cpu_usage: 10/10 replicas passed. Gate passed.