chore: utilize ensure_context decorator for Actor

[vdusek]

Utilize ensure_context decorator from Crawlee rather than calling raise_if_... method in the Actor class.

[janbuchar]

I'm honestly not sure about this. It reduces some duplication, yes, but the error message will be pretty cryptic. It is fine for an internal helper in Crawlee, but here, it's very much user-facing. Maybe we could make a wrapper for the decorator?

[vdusek]

Error message:

RuntimeError: The _ActorType is not active. Use it within the async context.

Whole traceback:

>>> asyncio.run(Actor.reboot())
Traceback (most recent call last):
  File "<python-input-5>", line 1, in <module>
    asyncio.run(Actor.reboot())
    ~~~~~~~~~~~^^^^^^^^^^^^^^^^
  File "/usr/lib64/python3.13/asyncio/runners.py", line 195, in run
    return runner.run(main)
           ~~~~~~~~~~^^^^^^
  File "/usr/lib64/python3.13/asyncio/runners.py", line 118, in run
    return self._loop.run_until_complete(task)
           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^
  File "/usr/lib64/python3.13/asyncio/base_events.py", line 725, in run_until_complete
    return future.result()
           ~~~~~~~~~~~~~^^
  File "/home/vdusek/Projects/apify-sdk-python/.venv/lib/python3.13/site-packages/crawlee/_utils/context.py", line 36, in async_wrapper
    raise RuntimeError(f'The {self.__class__.__name__} is not active. Use it within the async context.')
RuntimeError: The _ActorType is not active. Use it within the async context.

Is it that bad? We can wrap it of course.

[janbuchar]

Is it that bad? We can wrap it of course.

Well, leaking the existence of _ActorType is confusing by itself. Plus, the message should tell the user "Just use Actor.init or async with Actor" - many of them won't even know what a context manager is.

[Pijukatel]

I like this decorator, maybe we have to have custom error message in this case, but I think it makes the code more readable.

[vdusek]

Yep, I will try to update the decorator to have a better error message there.

[janbuchar]

Please wrap that error message 🙂

[vdusek]

Clousing, since we moved the flag(s) to the class level, and I'm afraid this means we can't utilize ensure_context now, as it relies on an instance-level attribute.