refactor(backend): Make block fields consistently use SchemaField

[majdyz]

Background

Currently, there are a lot of ways to define a field:

• Just write the type
• Use pydantic Field
• Use backend.data.model.SchemaField

The best way to define a field is to use the custom SchemaField which will allow us defining description, placeholder, and default values.

Changes 🏗️

Make all fields use SchemaField. And add check to prevent field defined without a SchemaField.

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: 3 🔵🔵🔵⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Potential Performance Issue The new code checks all fields in input_schema and output_schema, which could be inefficient for large schemas. Consider optimizing this check or performing it only when necessary. Possible Inconsistency The 'ratio', 'resolution', and 'frame_rate' fields are changed to use SchemaField, but their descriptions and default values remain the same. Ensure this change is intentional and consistent with other parts of the code. Naming Conflict The import 'from backend.data.model import SchemaField as Field' could lead to confusion as it shadows the original Field import. Consider using a different alias or keeping the original name.