[Backport 7.63.x] Normalize module path returned by get_go_module

[agent-platform-auto-pr]

Backport 978f3e2 from #34274.

---

<!--

• 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?

Normalize the path returned by the get_go_module function.

Motivation

On Windows the returned path would contain backslashes, meaning that in the following piece of code the condition to decide whether to skip the tests of a given module was always true as the modules.yml file uses posix paths:

datadog-agent/tasks/gotest.py

Lines 735 to 743 in 653f4b3

	modules_to_test = {}
	default_modules = get_default_modules()
	for package in packages:
	module_path = get_go_module(package)
	# Check if the module is in the target list of the modules we want to test
	if module_path not in default_modules or not default_modules[module_path].should_test():
	continue

This was causing Windows CI jobs not to run the unit tests for non-root Go modules on dev branches.

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.
-->

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]

Uncompressed package size comparison

Comparison with ancestor 1ac94d9c035cf3fddaa727935d2d6e2a6a847fcd

Diff per package

package	diff	status	size	ancestor	threshold
datadog-agent-aarch64-rpm	6.07MB	❌	932.56MB	926.50MB	0.50MB
datadog-agent-arm64-deb	6.06MB	❌	922.84MB	916.78MB	0.50MB
datadog-agent-x86_64-rpm	4.61MB	❌	943.92MB	939.31MB	0.50MB
datadog-agent-x86_64-suse	4.61MB	❌	943.92MB	939.31MB	0.50MB
datadog-agent-amd64-deb	4.61MB	❌	934.18MB	929.57MB	0.50MB
datadog-heroku-agent-amd64-deb	4.52MB	❌	482.41MB	477.89MB	0.50MB
datadog-dogstatsd-amd64-deb	0.02MB	⚠️	58.89MB	58.88MB	0.50MB
datadog-dogstatsd-x86_64-rpm	0.02MB	⚠️	58.97MB	58.95MB	0.50MB
datadog-dogstatsd-x86_64-suse	0.02MB	⚠️	58.97MB	58.95MB	0.50MB
datadog-dogstatsd-arm64-deb	0.01MB	⚠️	56.40MB	56.39MB	0.50MB
datadog-iot-agent-aarch64-rpm	0.01MB	⚠️	90.09MB	90.09MB	0.50MB
datadog-iot-agent-amd64-deb	0.01MB	⚠️	93.97MB	93.97MB	0.50MB
datadog-iot-agent-arm64-deb	0.01MB	⚠️	90.02MB	90.02MB	0.50MB
datadog-iot-agent-x86_64-rpm	0.01MB	⚠️	94.04MB	94.04MB	0.50MB
datadog-iot-agent-x86_64-suse	0.01MB	⚠️	94.04MB	94.04MB	0.50MB

Decision

❌ Failed

Currently this PR is blocked, you can reach out to #agent-delivery-help to get support/ask for an exception.

[cit-pr-commenter]

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: f7dabbbc-c9da-41e4-889c-fd53f202b336

Baseline: 27e4052
Comparison: d0cf87a
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	+3.43	[+0.30, +6.56]	1	Logs
➖	quality_gate_idle	memory utilization	+0.62	[+0.58, +0.65]	1	Logs bounds checks dashboard
➖	file_to_blackhole_1000ms_latency	egress throughput	+0.34	[-0.44, +1.11]	1	Logs
➖	file_to_blackhole_100ms_latency	egress throughput	+0.10	[-0.68, +0.87]	1	Logs
➖	file_to_blackhole_0ms_latency_http2	egress throughput	+0.06	[-0.71, +0.83]	1	Logs
➖	file_to_blackhole_500ms_latency	egress throughput	+0.06	[-0.73, +0.84]	1	Logs
➖	file_to_blackhole_300ms_latency	egress throughput	+0.00	[-0.63, +0.64]	1	Logs
➖	tcp_dd_logs_filter_exclude	ingress throughput	+0.00	[-0.03, +0.03]	1	Logs
➖	uds_dogstatsd_to_api	ingress throughput	-0.01	[-0.30, +0.29]	1	Logs
➖	file_to_blackhole_0ms_latency	egress throughput	-0.02	[-0.83, +0.78]	1	Logs
➖	file_tree	memory utilization	-0.03	[-0.09, +0.02]	1	Logs
➖	file_to_blackhole_0ms_latency_http1	egress throughput	-0.06	[-0.97, +0.85]	1	Logs
➖	file_to_blackhole_1000ms_latency_linear_load	egress throughput	-0.13	[-0.60, +0.34]	1	Logs
➖	quality_gate_idle_all_features	memory utilization	-0.19	[-0.23, -0.14]	1	Logs bounds checks dashboard
➖	uds_dogstatsd_to_api_cpu	% cpu utilization	-0.24	[-1.13, +0.65]	1	Logs
➖	tcp_syslog_to_blackhole	ingress throughput	-2.31	[-2.37, -2.24]	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_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 lost_bytes: 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 memory_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 intake_connections: 10/10 replicas passed. Gate passed.