fix(tests): stabilize Windows support expiry waits

[veryCrunchy]

Summary

• give the completed-receipt expiry test enough retention time for slower Windows runners
• give cancellation tests enough time to observe upload, reconciliation, and authoritative tombstone requests
• keep production support-intake behavior unchanged

Context

Follow-up to #351.

These support-intake tests failed in otherwise unrelated Windows checks for #399 and #403. They used two-second wall-clock boundaries around asynchronous HTTP handling; the Windows runner could legitimately cross those boundaries before the assertion observed the response.

Validation

On the dedicated build host:

• bash tools/check-repository.sh
• bash tools/test-prerelease-update-contract.sh
• focused reruns of JvmSupportIntakeTest.expiresCompletedReceiptWhileTheProcessRemainsOpen, JvmSupportIntakeTest.cancellationAfterUploadResponseCompletesSendsAuthoritativeTombstone, and JvmSupportIntakeTest.cancellationDuringReceiptReconciliationSendsAuthoritativeTombstone
• full :ui:desktopTest

The original two-test change was fully green, including hosted Windows. The added reconciliation test is being revalidated at ba8ca0fc1404a44d4d7c330f5258e35f471eb529.

[obiente-cloud]

Obiente preview

NC Native · ba8ca0fc1404 · Ready

Open preview

View in Obiente

_{Obiente updates this comment as the preview changes.}