[INCIDENT-50276] fix(kmt): Bump timeout used when downloading pulumi plugins

[Ishirui]

What does this PR do?

Bumps the timeout used when running go mod download while installing Pulumi plugins in KMT setup + add a verbose flag.

Motivation

incident-50276 - using ADMS as a GOPROXY, the go mod download can take more than 5mn, which causes the job to fail.

Describe how you validated your changes

Running CI

Additional Notes

Follow-up to #46178

[agent-platform-auto-pr]

Files inventory check summary

File checks results against ancestor 32dab88e:

Results for datadog-agent_7.78.0~devel.git.212.159797e.pipeline.99731661-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 ee698c3
📊 Static Quality Gates Dashboard
🔗 SQG Job

31 successful checks with minimal change (< 2 KiB)

	Quality gate	Current Size
✅	agent_deb_amd64	743.882 MiB
✅	agent_deb_amd64_fips	702.336 MiB
✅	agent_heroku_amd64	310.769 MiB
✅	agent_msi	607.854 MiB
✅	agent_rpm_amd64	743.866 MiB
✅	agent_rpm_amd64_fips	702.320 MiB
✅	agent_rpm_arm64	721.955 MiB
✅	agent_rpm_arm64_fips	683.438 MiB
✅	agent_suse_amd64	743.866 MiB
✅	agent_suse_amd64_fips	702.320 MiB
✅	agent_suse_arm64	721.955 MiB
✅	agent_suse_arm64_fips	683.438 MiB
✅	docker_agent_amd64	804.463 MiB
✅	docker_agent_arm64	807.350 MiB
✅	docker_agent_jmx_amd64	995.375 MiB
✅	docker_agent_jmx_arm64	987.044 MiB
✅	docker_cluster_agent_amd64	203.168 MiB
✅	docker_cluster_agent_arm64	217.646 MiB
✅	docker_cws_instrumentation_amd64	7.135 MiB
✅	docker_cws_instrumentation_arm64	6.689 MiB
✅	docker_dogstatsd_amd64	38.501 MiB
✅	docker_dogstatsd_arm64	36.812 MiB
✅	dogstatsd_deb_amd64	29.721 MiB
✅	dogstatsd_deb_arm64	27.881 MiB
✅	dogstatsd_rpm_amd64	29.721 MiB
✅	dogstatsd_suse_amd64	29.721 MiB
✅	iot_agent_deb_amd64	42.855 MiB
✅	iot_agent_deb_arm64	39.930 MiB
✅	iot_agent_deb_armhf	40.670 MiB
✅	iot_agent_rpm_amd64	42.856 MiB
✅	iot_agent_suse_amd64	42.856 MiB

On-wire sizes (compressed)

	Quality gate	Change	Size (prev → curr → max)
✅	agent_deb_amd64	-3.88 KiB (0.00% reduction)	173.787 → 173.783 → 177.700
✅	agent_deb_amd64_fips	-20.8 KiB (0.01% reduction)	164.644 → 164.624 → 172.230
✅	agent_heroku_amd64	neutral	74.941 MiB → 79.970
✅	agent_msi	+4.0 KiB (0.00% increase)	137.684 → 137.688 → 146.220
✅	agent_rpm_amd64	neutral	175.634 MiB → 180.780
✅	agent_rpm_amd64_fips	+11.44 KiB (0.01% increase)	167.513 → 167.524 → 173.370
✅	agent_rpm_arm64	neutral	157.965 MiB → 161.610
✅	agent_rpm_arm64_fips	+34.14 KiB (0.02% increase)	150.763 → 150.797 → 155.910
✅	agent_suse_amd64	neutral	175.634 MiB → 180.780
✅	agent_suse_amd64_fips	+11.44 KiB (0.01% increase)	167.513 → 167.524 → 173.370
✅	agent_suse_arm64	neutral	157.965 MiB → 161.610
✅	agent_suse_arm64_fips	+34.14 KiB (0.02% increase)	150.763 → 150.797 → 155.910
✅	docker_agent_amd64	neutral	266.129 MiB → 271.240
✅	docker_agent_arm64	neutral	253.418 MiB → 259.800
✅	docker_agent_jmx_amd64	neutral	334.777 MiB → 339.870
✅	docker_agent_jmx_arm64	+2.57 KiB (0.00% increase)	318.036 → 318.038 → 324.390
✅	docker_cluster_agent_amd64	neutral	71.108 MiB → 71.920
✅	docker_cluster_agent_arm64	neutral	66.757 MiB → 67.220
✅	docker_cws_instrumentation_amd64	neutral	2.995 MiB → 3.330
✅	docker_cws_instrumentation_arm64	neutral	2.726 MiB → 3.090
✅	docker_dogstatsd_amd64	neutral	14.900 MiB → 15.820
✅	docker_dogstatsd_arm64	neutral	14.233 MiB → 14.830
✅	dogstatsd_deb_amd64	neutral	7.852 MiB → 8.790
✅	dogstatsd_deb_arm64	neutral	6.742 MiB → 7.710
✅	dogstatsd_rpm_amd64	neutral	7.863 MiB → 8.800
✅	dogstatsd_suse_amd64	neutral	7.863 MiB → 8.800
✅	iot_agent_deb_amd64	neutral	11.301 MiB → 12.040
✅	iot_agent_deb_arm64	neutral	9.620 MiB → 10.450
✅	iot_agent_deb_armhf	neutral	9.849 MiB → 10.620
✅	iot_agent_rpm_amd64	neutral	11.319 MiB → 12.060
✅	iot_agent_suse_amd64	neutral	11.319 MiB → 12.060

[cit-pr-commenter-54b7da]

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: f4bff953-ad9f-43f7-a6c0-13a0bb9f9787

Baseline: 0bfbb9c
Comparison: 4db738e
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	+0.23	[-2.89, +3.35]	1	Logs

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	tcp_syslog_to_blackhole	ingress throughput	+1.58	[+1.51, +1.65]	1	Logs
➖	ddot_metrics_sum_delta	memory utilization	+0.48	[+0.29, +0.67]	1	Logs
➖	ddot_logs	memory utilization	+0.44	[+0.38, +0.50]	1	Logs
➖	quality_gate_metrics_logs	memory utilization	+0.30	[+0.09, +0.52]	1	Logs bounds checks dashboard
➖	docker_containers_memory	memory utilization	+0.29	[+0.21, +0.37]	1	Logs
➖	docker_containers_cpu	% cpu utilization	+0.23	[-2.89, +3.35]	1	Logs
➖	file_tree	memory utilization	+0.20	[+0.14, +0.25]	1	Logs
➖	otlp_ingest_logs	memory utilization	+0.09	[-0.00, +0.18]	1	Logs
➖	file_to_blackhole_0ms_latency	egress throughput	+0.06	[-0.39, +0.52]	1	Logs
➖	file_to_blackhole_500ms_latency	egress throughput	+0.02	[-0.35, +0.40]	1	Logs
➖	uds_dogstatsd_to_api_v3	ingress throughput	+0.00	[-0.12, +0.12]	1	Logs
➖	uds_dogstatsd_to_api	ingress throughput	-0.00	[-0.12, +0.12]	1	Logs
➖	quality_gate_idle	memory utilization	-0.01	[-0.05, +0.04]	1	Logs bounds checks dashboard
➖	tcp_dd_logs_filter_exclude	ingress throughput	-0.01	[-0.10, +0.08]	1	Logs
➖	file_to_blackhole_1000ms_latency	egress throughput	-0.01	[-0.43, +0.41]	1	Logs
➖	file_to_blackhole_100ms_latency	egress throughput	-0.06	[-0.10, -0.01]	1	Logs
➖	quality_gate_idle_all_features	memory utilization	-0.06	[-0.10, -0.02]	1	Logs bounds checks dashboard
➖	ddot_metrics_sum_cumulative	memory utilization	-0.12	[-0.28, +0.04]	1	Logs
➖	ddot_metrics	memory utilization	-0.12	[-0.32, +0.08]	1	Logs
➖	ddot_metrics_sum_cumulativetodelta_exporter	memory utilization	-0.21	[-0.44, +0.02]	1	Logs
➖	otlp_ingest_metrics	memory utilization	-0.27	[-0.42, -0.12]	1	Logs
➖	uds_dogstatsd_20mb_12k_contexts_20_senders	memory utilization	-0.33	[-0.38, -0.28]	1	Logs
➖	quality_gate_logs	% cpu utilization	-1.70	[-3.18, -0.23]	1	Logs bounds checks dashboard

Bounds Checks: ✅ Passed

perf	experiment	bounds_check_name	replicates_passed	links
✅	docker_containers_cpu	simple_check_run	10/10
✅	docker_containers_memory	memory_usage	10/10
✅	docker_containers_memory	simple_check_run	10/10
✅	file_to_blackhole_0ms_latency	lost_bytes	10/10
✅	file_to_blackhole_0ms_latency	memory_usage	10/10
✅	file_to_blackhole_1000ms_latency	lost_bytes	10/10
✅	file_to_blackhole_1000ms_latency	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_500ms_latency	lost_bytes	10/10
✅	file_to_blackhole_500ms_latency	memory_usage	10/10
✅	quality_gate_idle	intake_connections	10/10	bounds checks dashboard
✅	quality_gate_idle	memory_usage	10/10	bounds checks dashboard
✅	quality_gate_idle_all_features	intake_connections	10/10	bounds checks dashboard
✅	quality_gate_idle_all_features	memory_usage	10/10	bounds checks dashboard
✅	quality_gate_logs	intake_connections	10/10	bounds checks dashboard
✅	quality_gate_logs	lost_bytes	10/10	bounds checks dashboard
✅	quality_gate_logs	memory_usage	10/10	bounds checks dashboard
✅	quality_gate_metrics_logs	cpu_usage	10/10	bounds checks dashboard
✅	quality_gate_metrics_logs	intake_connections	10/10	bounds checks dashboard
✅	quality_gate_metrics_logs	lost_bytes	10/10	bounds checks dashboard
✅	quality_gate_metrics_logs	memory_usage	10/10	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_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_logs, bounds check intake_connections: 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_metrics_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
• quality_gate_idle, bounds check intake_connections: 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.
• quality_gate_idle_all_features, bounds check intake_connections: 10/10 replicas passed. Gate passed.