[ABLD-8] Add //:release config setting

[aiuto]

What does this PR do?

Creates a bazel flag to indicate we should do all the optimizations that we would for a release build.

Motivation

As we build start doing the packaging rules for deb/rpm files with Bazel, we will need simple ways to trigger the things that are specific to release builds as opposed to developer builds. Other PRs in fight can use this to select expensive tasks such as signing binaries or compressing tarballs in packages

Also: [ABLD-399]

[agent-platform-auto-pr]

Files inventory check summary

File checks results against ancestor f171f06c:

Results for datadog-agent_7.79.0~devel.git.319.76e730d.pipeline.105341546-1_amd64.deb:

No change detected

[agent-platform-auto-pr]

Static quality checks

✅ Please find below the results from static quality gates
Comparison made with ancestor f171f06
📊 Static Quality Gates Dashboard
🔗 SQG Job

31 successful checks with minimal change (< 2 KiB)

	Quality gate	Current Size
✅	agent_deb_amd64	753.073 MiB
✅	agent_deb_amd64_fips	710.012 MiB
✅	agent_heroku_amd64	313.321 MiB
✅	agent_msi	604.870 MiB
✅	agent_rpm_amd64	753.057 MiB
✅	agent_rpm_amd64_fips	709.996 MiB
✅	agent_rpm_arm64	731.476 MiB
✅	agent_rpm_arm64_fips	691.432 MiB
✅	agent_suse_amd64	753.057 MiB
✅	agent_suse_amd64_fips	709.996 MiB
✅	agent_suse_arm64	731.476 MiB
✅	agent_suse_arm64_fips	691.432 MiB
✅	docker_agent_amd64	813.376 MiB
✅	docker_agent_arm64	816.565 MiB
✅	docker_agent_jmx_amd64	1004.291 MiB
✅	docker_agent_jmx_arm64	996.259 MiB
✅	docker_cluster_agent_amd64	203.957 MiB
✅	docker_cluster_agent_arm64	218.419 MiB
✅	docker_cws_instrumentation_amd64	7.142 MiB
✅	docker_cws_instrumentation_arm64	6.689 MiB
✅	docker_dogstatsd_amd64	39.234 MiB
✅	docker_dogstatsd_arm64	37.445 MiB
✅	dogstatsd_deb_amd64	29.878 MiB
✅	dogstatsd_deb_arm64	28.030 MiB
✅	dogstatsd_rpm_amd64	29.878 MiB
✅	dogstatsd_suse_amd64	29.878 MiB
✅	iot_agent_deb_amd64	43.285 MiB
✅	iot_agent_deb_arm64	40.332 MiB
✅	iot_agent_deb_armhf	41.084 MiB
✅	iot_agent_rpm_amd64	43.286 MiB
✅	iot_agent_suse_amd64	43.286 MiB

On-wire sizes (compressed)

	Quality gate	Change	Size (prev → curr → max)
✅	agent_deb_amd64	+28.21 KiB (0.02% increase)	174.756 → 174.784 → 178.360
✅	agent_deb_amd64_fips	+20.84 KiB (0.01% increase)	165.392 → 165.412 → 172.790
✅	agent_heroku_amd64	neutral	74.999 MiB → 79.970
✅	agent_msi	neutral	138.391 MiB → 146.220
✅	agent_rpm_amd64	+27.41 KiB (0.02% increase)	177.619 → 177.646 → 181.830
✅	agent_rpm_amd64_fips	-10.87 KiB (0.01% reduction)	167.709 → 167.698 → 173.370
✅	agent_rpm_arm64	-11.3 KiB (0.01% reduction)	159.543 → 159.532 → 163.060
✅	agent_rpm_arm64_fips	+32.08 KiB (0.02% increase)	151.397 → 151.428 → 156.170
✅	agent_suse_amd64	+27.41 KiB (0.02% increase)	177.619 → 177.646 → 181.830
✅	agent_suse_amd64_fips	-10.87 KiB (0.01% reduction)	167.709 → 167.698 → 173.370
✅	agent_suse_arm64	-11.3 KiB (0.01% reduction)	159.543 → 159.532 → 163.060
✅	agent_suse_arm64_fips	+32.08 KiB (0.02% increase)	151.397 → 151.428 → 156.170
✅	docker_agent_amd64	neutral	268.192 MiB → 272.480
✅	docker_agent_arm64	neutral	255.391 MiB → 261.060
✅	docker_agent_jmx_amd64	neutral	336.842 MiB → 341.100
✅	docker_agent_jmx_arm64	-3.52 KiB (0.00% reduction)	320.026 → 320.023 → 325.620
✅	docker_cluster_agent_amd64	neutral	71.375 MiB → 72.920
✅	docker_cluster_agent_arm64	neutral	67.010 MiB → 68.220
✅	docker_cws_instrumentation_amd64	neutral	2.999 MiB → 3.330
✅	docker_cws_instrumentation_arm64	neutral	2.729 MiB → 3.090
✅	docker_dogstatsd_amd64	neutral	15.174 MiB → 15.820
✅	docker_dogstatsd_arm64	neutral	14.490 MiB → 14.830
✅	dogstatsd_deb_amd64	neutral	7.894 MiB → 8.790
✅	dogstatsd_deb_arm64	neutral	6.777 MiB → 7.710
✅	dogstatsd_rpm_amd64	neutral	7.906 MiB → 8.800
✅	dogstatsd_suse_amd64	neutral	7.906 MiB → 8.800
✅	iot_agent_deb_amd64	neutral	11.402 MiB → 12.040
✅	iot_agent_deb_arm64	neutral	9.703 MiB → 10.450
✅	iot_agent_deb_armhf	neutral	9.941 MiB → 10.620
✅	iot_agent_rpm_amd64	-2.49 KiB (0.02% reduction)	11.420 → 11.418 → 12.060
✅	iot_agent_suse_amd64	-2.49 KiB (0.02% reduction)	11.420 → 11.418 → 12.060

[cit-pr-commenter-54b7da]

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: a0a13f68-2bff-485a-9642-184e341bb1e3

Baseline: f171f06
Comparison: 76e730d
Diff

Optimization Goals: ✅ No significant changes detected

Experiments ignored for regressions

Regressions in experiments with settings containing erratic: true are ignored.

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	docker_containers_cpu	% cpu utilization	+3.34	[+0.32, +6.35]	1	Logs

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	docker_containers_cpu	% cpu utilization	+3.34	[+0.32, +6.35]	1	Logs
➖	ddot_metrics_sum_cumulative	memory utilization	+0.67	[+0.52, +0.81]	1	Logs
➖	file_tree	memory utilization	+0.39	[+0.33, +0.45]	1	Logs
➖	quality_gate_idle	memory utilization	+0.36	[+0.31, +0.41]	1	Logs bounds checks dashboard
➖	ddot_metrics_sum_cumulativetodelta_exporter	memory utilization	+0.36	[+0.14, +0.58]	1	Logs
➖	file_to_blackhole_100ms_latency	egress throughput	+0.07	[-0.02, +0.16]	1	Logs
➖	file_to_blackhole_500ms_latency	egress throughput	+0.06	[-0.32, +0.44]	1	Logs
➖	otlp_ingest_metrics	memory utilization	+0.04	[-0.13, +0.21]	1	Logs
➖	file_to_blackhole_0ms_latency	egress throughput	+0.02	[-0.46, +0.51]	1	Logs
➖	ddot_metrics	memory utilization	+0.01	[-0.17, +0.19]	1	Logs
➖	uds_dogstatsd_to_api_v3	ingress throughput	+0.01	[-0.19, +0.20]	1	Logs
➖	file_to_blackhole_1000ms_latency	egress throughput	+0.01	[-0.42, +0.43]	1	Logs
➖	uds_dogstatsd_to_api	ingress throughput	+0.00	[-0.20, +0.20]	1	Logs
➖	tcp_dd_logs_filter_exclude	ingress throughput	-0.00	[-0.11, +0.10]	1	Logs
➖	uds_dogstatsd_20mb_12k_contexts_20_senders	memory utilization	-0.16	[-0.22, -0.10]	1	Logs
➖	quality_gate_logs	% cpu utilization	-0.17	[-1.73, +1.39]	1	Logs bounds checks dashboard
➖	ddot_metrics_sum_delta	memory utilization	-0.25	[-0.42, -0.08]	1	Logs
➖	ddot_logs	memory utilization	-0.34	[-0.40, -0.28]	1	Logs
➖	quality_gate_idle_all_features	memory utilization	-0.34	[-0.38, -0.31]	1	Logs bounds checks dashboard
➖	quality_gate_metrics_logs	memory utilization	-0.69	[-0.93, -0.46]	1	Logs bounds checks dashboard
➖	otlp_ingest_logs	memory utilization	-0.69	[-0.79, -0.59]	1	Logs
➖	docker_containers_memory	memory utilization	-0.74	[-0.80, -0.67]	1	Logs
➖	tcp_syslog_to_blackhole	ingress throughput	-1.43	[-1.58, -1.28]	1	Logs

Bounds Checks: ❌ Failed

perf	experiment	bounds_check_name	replicates_passed	observed_value	links
✅	docker_containers_cpu	simple_check_run	10/10	705 ≥ 26
✅	docker_containers_memory	memory_usage	10/10	270.50MiB ≤ 370MiB
✅	docker_containers_memory	simple_check_run	10/10	691 ≥ 26
✅	file_to_blackhole_0ms_latency	memory_usage	10/10	0.19GiB ≤ 1.20GiB
✅	file_to_blackhole_0ms_latency	missed_bytes	10/10	0B = 0B
✅	file_to_blackhole_1000ms_latency	memory_usage	10/10	0.23GiB ≤ 1.20GiB
✅	file_to_blackhole_1000ms_latency	missed_bytes	10/10	0B = 0B
✅	file_to_blackhole_100ms_latency	memory_usage	10/10	0.19GiB ≤ 1.20GiB
✅	file_to_blackhole_100ms_latency	missed_bytes	10/10	0B = 0B
✅	file_to_blackhole_500ms_latency	memory_usage	10/10	0.21GiB ≤ 1.20GiB
✅	file_to_blackhole_500ms_latency	missed_bytes	10/10	0B = 0B
✅	quality_gate_idle	intake_connections	10/10	3 = 3	bounds checks dashboard
❌	quality_gate_idle	memory_usage	9/10	175.30MiB > 175MiB	bounds checks dashboard
✅	quality_gate_idle_all_features	intake_connections	10/10	3 = 3	bounds checks dashboard
✅	quality_gate_idle_all_features	memory_usage	10/10	490.28MiB ≤ 550MiB	bounds checks dashboard
✅	quality_gate_logs	intake_connections	10/10	4 ≤ 6	bounds checks dashboard
✅	quality_gate_logs	memory_usage	10/10	202.27MiB ≤ 220MiB	bounds checks dashboard
✅	quality_gate_logs	missed_bytes	10/10	0B = 0B	bounds checks dashboard
✅	quality_gate_metrics_logs	cpu_usage	10/10	350.98 ≤ 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	401.93MiB ≤ 475MiB	bounds checks dashboard
✅	quality_gate_metrics_logs	missed_bytes	10/10	0B = 0B	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

❌ Failed. Some Quality Gates were violated.

• quality_gate_idle, bounds check intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_idle, bounds check memory_usage: 9/10 replicas passed. Failed 1 which is > 0. Gate FAILED.
• quality_gate_metrics_logs, bounds check intake_connections: 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 cpu_usage: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, 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.
• quality_gate_idle_all_features, 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_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.