fix: reconnect to platform events websocket after connection drop

[vdusek]

• Previously, ApifyEventManager._process_platform_messages connected to the platform events websocket exactly once. Any dropped connection raised ConnectionClosedError and permanently ended the processing task, while a graceful server-side close exited silently. In both cases, the Actor missed all subsequent platform events for the rest of the run.
• The connection now uses the websockets reconnect iterator, which re-establishes the connection after every drop or graceful close, with backoff on failed attempts. An abnormal drop is logged as a warning and a graceful close as info, both with the close code and reason, and a successful reconnect is logged as well.
• A process_exception callback keeps errors fatal before the first successful connection, so Actor.init still fails fast on a misconfigured URL instead of hanging. After the first connection, the default websockets classification decides which errors are transient and retried.
• __aexit__ now cancels the processing task before closing the websocket. Otherwise, every clean shutdown would trigger a spurious reconnect attempt.
• Added a regression test, parametrized over graceful and abnormal closes, that drops the connection server-side and asserts the drop is logged, the client reconnects, and events keep arriving. It replaces the obsolete mid-stream disconnect test, whose premise (the task ends after a drop) no longer holds.

[codecov]

Codecov Report

❌ Patch coverage is 98.21429% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 90.43%. Comparing base (0daca28) to head (3ba124d).
⚠️ Report is 18 commits behind head on master.

Files with missing lines	Patch %	Lines
src/apify/events/_apify_event_manager.py	98.21%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #967      +/-   ##
==========================================
+ Coverage   89.90%   90.43%   +0.53%     
==========================================
  Files          49       49              
  Lines        3091     3127      +36     
==========================================
+ Hits         2779     2828      +49     
+ Misses        312      299      -13     

Flag	Coverage Δ
e2e	36.16% <21.42%> (+0.25%)	⬆️
integration	57.11% <21.42%> (+0.24%)	⬆️
unit	79.18% <98.21%> (+0.43%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Pijukatel]

Some Claude spam...

[Pijukatel]

Is this implemented in JS? If not, is there a parity issue?

[vdusek]

Is this implemented in JS? If not, is there a parity issue?

I'll open it.