fix(backend): Avoid long synchronous call to block FastAPI event-loop

[majdyz]

Background

We are doing some synchronous calls (pyro calls) on our FastAPI handler, which can potentially block the event loop and render the API unavailable.

Changes 🏗️

• Remove async on function handlers that call pyro & don't require async calls.
• Uses asyncio.to_thread to execute pyro calls that mix with async calls.

Testing 🔍

Note

Only for the new autogpt platform, currently in autogpt_platform/

• Create from scratch and execute an agent with at least 3 blocks
• Import an agent from file upload, and confirm it executes correctly
• Upload agent to marketplace
• Import an agent from marketplace and confirm it executes correctly
• Edit an agent from monitor, and confirm it executes correctly

[qodo-merge-pro]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Potential Race Condition The use of asyncio.to_thread for canceling execution might introduce a race condition if the cancellation is not handled properly in the execution manager. Error Handling The execute_graph method has been changed from async to sync, but there's no error handling for potential exceptions that might occur during execution. Async/Sync Mismatch The execute_graph call has been changed from async to sync, but it's still being used in an async context. This might lead to unexpected behavior.