feat: resume runtime on fired triggers

[radu-mocanu]

• resume runtime on fired triggers

[Copilot]

Pull request overview

Adds “auto-resume” behavior to the resumable runtime so that if resume triggers are already fired at the time of suspension, the runtime immediately resumes without requiring an external resume call.

Changes:

• Implement auto-resume flow in UiPathResumableRuntime.execute() and .stream() when fired triggers are detected.
• Introduce UiPathSuspensionResult to carry both the suspension UiPathRuntimeResult and any fired trigger resume-map.
• Add async tests covering auto-resume scenarios (none/partial/all fired; multiple auto-resumes; stream behavior).

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 6 comments.

File	Description
src/uipath/runtime/resumable/runtime.py	Adds fired-trigger detection at suspension time and recursive auto-resume for execute() and stream().
src/uipath/runtime/result.py	Adds UiPathSuspensionResult model used to return both runtime result and fired trigger map.
tests/test_resumable.py	Adds coverage for auto-resume behavior across several trigger-firing patterns.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[cristipufu]

execution_completed = False
while not execution_completed

and change the return with

execution_completed = True

I remember issues with returning during a while loop in an async generator

[cristipufu]

We either use is_suspended everywhere or just check for UiPathRuntimeStatus everywhere (I would incline towards the latter in this low-level concepts)

[radu-mocanu]

good catch, forgot to replace it here.
I would rollback to the UiPathRuntimeStatus check to keep the runtime more explicit