fix: handle TimeoutError in Actor __aexit__ to prevent resource leaks

When Actor cleanup exceeded `_cleanup_timeout`, the unhandled
`TimeoutError` from `asyncio.wait_for` left the Actor in a broken
state: `_is_initialized` was never reset, event/charging managers
were left partially shut down, and `sys.exit()` was never called.

Now the timeout is caught and critical resource cleanup (event manager,
charging manager) is attempted even after timeout. `_is_initialized`
is reset in a `finally` block to guarantee consistent state.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: vdusek

src/apify/_actor.py

@@ -252,8 +252,17 @@ async def finalize() -> None:
             # Persist Actor state
             await self._save_actor_state()
 
-        await asyncio.wait_for(finalize(), self._cleanup_timeout.total_seconds())
-        self._is_initialized = False
+        try:
+            await asyncio.wait_for(finalize(), self._cleanup_timeout.total_seconds())
+        except TimeoutError:
+            self.log.warning('Actor cleanup timed out, forcing shutdown of event manager and charging manager')
+            # Ensure critical resources are cleaned up even after timeout
+            with suppress(Exception):
+                await self.event_manager.__aexit__(None, None, None)
+            with suppress(Exception):
+                await self._charging_manager_implementation.__aexit__(None, None, None)
+        finally:
+            self._is_initialized = False
 
         if self._exit_process:
             sys.exit(self.exit_code)