Delete all alarms on abortAllDurableObjects()

[mrbbot]

Fixes cloudflare/workers-sdk#5388

In the Workers Vitest integration, we call the abortAllDurableObjects() function after each test to abort all Durable Objects and close all SQLite databases. If the isolated storage option is enabled, we backup/restore .sqlite files to automatically undo writes performed in tests. Right now, this doesn't cancel Durable Object alarms. This means that an alarm scheduled in one test might end up firing when another later test is running. This could lead to unexpected test results, and non-determinism in tests.

This PR addresses this issue by automatically deleting all Durable Object alarms when abortAllDurableObjects() is called. This is a local-only internal API that's currently only used in the Vitest integration, so making this breaking change is fine. 👍

[allan-simon]

is there a reason why this PR was not merged, it would help solve the known issue of vitest integration ?

If necessary I can reopen a similar PR rebased on latest master if @mrbbot has not the time ?

[codspeed-hq]

Merging this PR will improve performance by 26.77%

⚡ 1 improved benchmark
✅ 69 untouched benchmarks
⏩ 129 skipped benchmarks¹

Performance Changes

	Benchmark	BASE	HEAD	Efficiency
⚡	bodyWithHeaders[Response]	38.2 µs	30.1 µs	+26.77%

---

_{Comparing bcoll/abort-all-durable-object-alarms (4aa850a) with main (cce9f17)}

Footnotes

1. 129 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[kentonv]

Ironically, a week after this PR was merged, vitest-pool-workers actually removed its usage of this API. After two years of waiting...

And after some discussion, we feel that it doesn't make sense for abortAllDurableObjects() to cancel alarms. Cancelling alarms is essentially deleting data from the DOs, but since it doesn't delete all data, it leaves them in an inconsistent state.

It could make sense to add a new deleteAllDurableObjects() API which aborts DOs, cancels alarms, and deletes underlying data, but that should be a separate API.

In any case I will be rolling this back as it is blocking #6104.