Abort timers when log wait strategy completes

[cristianrgreco]

Fixes #982

To reproduce this we need to run the reaper container which invokes Wait.forLogMessage(). This MUST be done in vitest's globalSetup. Unlike setupFiles or in an individual test, vitest will wait for all processes to complete before shutting down.

The issue is introduced here: https://github.com/testcontainers/testcontainers-node/pull/977/files#diff-586d44bcd7d69ec116da37a953ccb21b6d22a17c3977e1b98eb487870b899007R20

The setTimeout runs in the background even after the reaper container has started, preventing the process from exiting. This PR incorporates abort signals between the setTimeout and the resolution of the log message, to ensure that when one succeeds, the other is aborted.

Struggling to add a test for this.

---

Tempted to simply revert the commit instead of try to fix forward, in case more issues are introduced: #984

[netlify]

✅ Deploy Preview for testcontainers-node ready!

Name	Link
🔨 Latest commit	da4ed3f
🔍 Latest deploy log	https://app.netlify.com/sites/testcontainers-node/deploys/67f798025473350008193653
😎 Deploy Preview	https://deploy-preview-983--testcontainers-node.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.