[Backport 7.64.x] Fix agent's version-manifests

[agent-platform-auto-pr]

Backport 9330bf1 from #34245.

---

<!--

• Contributors are encouraged to read our CONTRIBUTING documentation.
• Both Contributor and Reviewer Checklists are available at https://datadoghq.dev/datadog-agent/guidelines/contributing/#pull-requests.
• The pull request:
  • Should only fix one issue or add one feature at a time.
  • Must update the test suite for the relevant functionality.
  • Should pass all status checks before being reviewed or merged.
• Commit titles should be prefixed with general area of pull request's change.
• Please fill the below sections if possible with relevant information or links.
  -->

What does this PR do?

Fix incorrect version manifest being generated and packaged.

Motivation

The version-manifest.txt & version-manifest.json files we ship in our packages are broken since we started splitting build & packaging.
This is because omnibus will systematically generate those files based on the software that were build for the current project.
When packaging, we only have 2 softwares being built, and we end up overriding the manifests generated during the build jobs with incorrect ones.
This PR fixes this.

Describe how you validated your changes

<!--
Validate your changes before merge, ensuring that:

• Your PR is tested by static / unit / integrations / e2e tests
• Your PR description details which e2e tests cover your changes, if any
• The PR description contains details of how you validated your changes. If you validated changes manually and not through automated tests, add context on why automated tests did not fit your changes validation.

If you want additional validation by a second person, you can ask reviewers to do it. Describe how to set up an environment for manual tests in the PR description. Manual validation is expected to happen on every commit before merge.

Any manual validation step should then map to an automated test. Manual validation should not substitute automation, minus exceptions not supported by test tooling yet.
-->

Will be verified manually once the pipeline for this PR completes

Possible Drawbacks / Trade-offs

Additional Notes

<!--

• Anything else we should know when reviewing?
• Include benchmarking information here whenever possible.
• Include info about alternatives that were considered and why the proposed
  version was chosen.
  -->

[agent-platform-auto-pr]

[Fast Unit Tests Report]

On pipeline 56534152 (CI Visibility). The following jobs did not run any unit tests:

Jobs:

• tests_deb-arm64-py3
• tests_deb-x64-py3
• tests_flavor_dogstatsd_deb-x64
• tests_flavor_heroku_deb-x64
• tests_flavor_iot_deb-x64
• tests_rpm-arm64-py3
• tests_rpm-x64-py3
• tests_windows-x64

If you modified Go files and expected unit tests to run in these jobs, please double check the job logs. If you think tests should have been executed reach out to #agent-devx-help

[agent-platform-auto-pr]

Uncompressed package size comparison

Comparison with ancestor 6205bcf815e98e57d6d7d4125fe4f43f9812e12d

Diff per package

package	diff	status	size	ancestor	threshold
datadog-agent-amd64-deb	0.04MB	⚠️	869.07MB	869.02MB	0.50MB
datadog-agent-arm64-deb	0.04MB	⚠️	858.38MB	858.34MB	0.50MB
datadog-agent-x86_64-rpm	0.04MB	⚠️	878.83MB	878.79MB	0.50MB
datadog-agent-x86_64-suse	0.04MB	⚠️	878.83MB	878.79MB	0.50MB
datadog-agent-aarch64-rpm	0.04MB	⚠️	868.13MB	868.09MB	0.50MB
datadog-dogstatsd-amd64-deb	0.00MB	✅	41.40MB	41.40MB	0.50MB
datadog-dogstatsd-x86_64-rpm	0.00MB	✅	41.48MB	41.48MB	0.50MB
datadog-dogstatsd-x86_64-suse	0.00MB	✅	41.48MB	41.48MB	0.50MB
datadog-dogstatsd-arm64-deb	0.00MB	✅	39.66MB	39.66MB	0.50MB
datadog-iot-agent-amd64-deb	0.00MB	✅	62.02MB	62.02MB	0.50MB
datadog-iot-agent-x86_64-rpm	0.00MB	✅	62.09MB	62.09MB	0.50MB
datadog-iot-agent-x86_64-suse	0.00MB	✅	62.09MB	62.09MB	0.50MB
datadog-iot-agent-arm64-deb	0.00MB	✅	59.26MB	59.26MB	0.50MB
datadog-iot-agent-aarch64-rpm	0.00MB	✅	59.33MB	59.33MB	0.50MB
datadog-heroku-agent-amd64-deb	-0.02MB	✅	446.32MB	446.34MB	0.50MB

Decision

⚠️ Warning

[agent-platform-auto-pr]

Static quality checks ✅

Please find below the results from static quality gates

Successful checks

Info

Result	Quality gate	On disk size	On disk size limit	On wire size	On wire size limit
✅	static_quality_gate_agent_deb_amd64	840.16MiB	847.49MiB	203.02MiB	212.33MiB
✅	static_quality_gate_agent_deb_arm64	829.95MiB	836.66MiB	184.22MiB	192.5MiB
✅	static_quality_gate_agent_rpm_amd64	840.15MiB	847.82MiB	205.96MiB	215.76MiB
✅	static_quality_gate_agent_rpm_arm64	829.94MiB	836.66MiB	185.34MiB	194.24MiB
✅	static_quality_gate_agent_suse_amd64	840.15MiB	847.82MiB	205.96MiB	215.76MiB
✅	static_quality_gate_agent_suse_arm64	829.94MiB	836.66MiB	185.34MiB	194.24MiB
✅	static_quality_gate_dogstatsd_deb_amd64	39.56MiB	49.7MiB	10.55MiB	20.6MiB
✅	static_quality_gate_dogstatsd_deb_arm64	37.9MiB	48.1MiB	9.13MiB	19.1MiB
✅	static_quality_gate_dogstatsd_rpm_amd64	39.56MiB	49.7MiB	10.56MiB	20.6MiB
✅	static_quality_gate_dogstatsd_suse_amd64	39.56MiB	49.7MiB	10.56MiB	20.6MiB
✅	static_quality_gate_iot_agent_deb_amd64	59.22MiB	69.0MiB	14.88MiB	24.8MiB
✅	static_quality_gate_iot_agent_deb_arm64	56.59MiB	66.4MiB	12.85MiB	22.8MiB
✅	static_quality_gate_iot_agent_rpm_amd64	59.22MiB	69.0MiB	14.9MiB	24.8MiB
✅	static_quality_gate_iot_agent_rpm_arm64	56.59MiB	66.4MiB	12.85MiB	22.8MiB
✅	static_quality_gate_iot_agent_suse_amd64	59.22MiB	69.0MiB	14.9MiB	24.8MiB
✅	static_quality_gate_docker_agent_amd64	924.93MiB	931.7MiB	309.07MiB	318.67MiB
✅	static_quality_gate_docker_agent_arm64	938.0MiB	944.08MiB	294.06MiB	303.0MiB
✅	static_quality_gate_docker_agent_jmx_amd64	1.1GiB	1.1GiB	384.18MiB	393.75MiB
✅	static_quality_gate_docker_agent_jmx_arm64	1.1GiB	1.1GiB	365.15MiB	373.71MiB
✅	static_quality_gate_docker_dogstatsd_amd64	47.7MiB	57.88MiB	18.26MiB	28.29MiB
✅	static_quality_gate_docker_dogstatsd_arm64	46.09MiB	56.27MiB	17.02MiB	27.06MiB
✅	static_quality_gate_docker_cluster_agent_amd64	264.95MiB	274.78MiB	106.33MiB	116.28MiB
✅	static_quality_gate_docker_cluster_agent_arm64	280.92MiB	290.82MiB	101.17MiB	111.12MiB

[cit-pr-commenter]

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: c2717739-6850-406a-b3b6-b3d37523e9dc

Baseline: 6205bcf
Comparison: 866733b
Diff

Optimization Goals: ✅ No significant changes detected

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	quality_gate_logs	% cpu utilization	+1.74	[-1.26, +4.75]	1	Logs
➖	quality_gate_idle	memory utilization	+0.66	[+0.60, +0.71]	1	Logs bounds checks dashboard
➖	tcp_syslog_to_blackhole	ingress throughput	+0.63	[+0.57, +0.68]	1	Logs
➖	uds_dogstatsd_to_api_cpu	% cpu utilization	+0.44	[-0.45, +1.34]	1	Logs
➖	file_to_blackhole_1000ms_latency	egress throughput	+0.29	[-0.53, +1.11]	1	Logs
➖	quality_gate_idle_all_features	memory utilization	+0.12	[+0.06, +0.17]	1	Logs bounds checks dashboard
➖	file_to_blackhole_0ms_latency	egress throughput	+0.03	[-0.79, +0.84]	1	Logs
➖	file_to_blackhole_0ms_latency_http1	egress throughput	+0.02	[-0.75, +0.79]	1	Logs
➖	uds_dogstatsd_to_api	ingress throughput	+0.01	[-0.27, +0.30]	1	Logs
➖	file_to_blackhole_0ms_latency_http2	egress throughput	+0.01	[-0.80, +0.81]	1	Logs
➖	tcp_dd_logs_filter_exclude	ingress throughput	+0.00	[-0.03, +0.03]	1	Logs
➖	file_to_blackhole_100ms_latency	egress throughput	-0.01	[-0.63, +0.62]	1	Logs
➖	file_to_blackhole_300ms_latency	egress throughput	-0.04	[-0.67, +0.59]	1	Logs
➖	file_to_blackhole_500ms_latency	egress throughput	-0.08	[-0.87, +0.71]	1	Logs
➖	file_to_blackhole_1000ms_latency_linear_load	egress throughput	-0.14	[-0.60, +0.32]	1	Logs
➖	file_tree	memory utilization	-0.20	[-0.26, -0.13]	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	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
✅	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, 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.
• 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.