Fix flaky KubernetesInformerCreatorTest on Windows due to shared semaphore race condition

[Copilot]

KubernetesInformerCreatorTest.informerInjection fails on Windows because both the pod and configmap watch stubs shared a single watchCount semaphore. On Windows, the pod informer can complete LIST→WATCH, receive the empty {} response, and immediately loop back to fire a second WATCH — all before the configmap informer makes its first WATCH request. Two pod-watch firings then satisfy watchCount.acquire(2), letting the test advance to verify() before the configmap watch ever happens.

Changes

• Per-stub CountDownLatch(1) instead of shared Semaphore: replaced getCount/watchCount (shared across both informers) with four independent latches — podGetLatch, podWatchLatch, configMapGetLatch, configMapWatchLatch — each wired to its own stub
• Idempotent signaling: CountDownLatch.countDown() is a no-op once at zero, so repeated firings from one informer cannot accidentally satisfy another informer's gate
• Updated CountRequestAction: switched from Semaphore.release() to CountDownLatch.countDown()

// Before: shared semaphores — pod watch firing twice satisfies watchCount.acquire(2)
Semaphore watchCount = new Semaphore(2);
watchParams.put("semaphore", watchCount); // same params for BOTH pod and configmap stubs

// After: independent latches — each informer's watch must fire at least once
CountDownLatch podWatchLatch = new CountDownLatch(1);
CountDownLatch configMapWatchLatch = new CountDownLatch(1);
podWatchParams.put("semaphore", podWatchLatch);
configMapWatchParams.put("semaphore", configMapWatchLatch);
// ...
podWatchLatch.await();
configMapWatchLatch.await();

Original prompt

Fix the failing GitHub Actions workflow Java 21.0.x Maven Test on windows-latest
Analyze the workflow logs, identify the root cause of the failure, and implement a fix.
Job ID: 64092008585
Job URL: https://github.com/kubernetes-client/java/actions/runs/22165572207/job/64092008585

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Copilot
Once this PR has been reviewed and has the lgtm label, please ask for approval from brendandburns. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment