CI Flake for Windows?

# 🐞 bug report

### Affected Rule

N/A

### Is this a regression?

Unsure

### Description

Windows CI seems to be a bit flaky (flakey? what's the preferred spelling? Well added both here for future searches lol).

In #3179 I had @jbedard push a couple empty commits. In order:

1. **Passing** CI for the last real commit in the PR https://github.com/bazel-contrib/rules_python/pull/3179/commits/8476820c710f122161577720c18e2b8e8ef4e144: https://buildkite.com/bazel/rules-python-python/builds/12586/steps/canvas
2. Pushed empty commit resulted in CI **failure** https://github.com/bazel-contrib/rules_python/pull/3179/commits/0910362b4bdaf32422b21b6fe9d6d65c7dc2bd06: https://buildkite.com/bazel/rules-python-python/builds/12587/steps/canvas
3. Pushed another empty commit resulted in CI **pass** https://github.com/bazel-contrib/rules_python/pull/3179/commits/fdbb53eadee1af1fa0910836db54dac2c76857e0: https://buildkite.com/bazel/rules-python-python/builds/12588/steps/canvas

首先比较 PR #3179 关联的 Buildkite 运行 12586、12587 和 12588，重点关注通过的空提交与失败的空提交之间发生了什么变化。Issue 未指出失败的步骤或预期的修复，因此必须在隔离间歇性 Windows CI 的原因后确定完成标准。

由索引模型根据 Issue 内容生成。