fix(backend): Add execution persistence for execution scheduler service

[majdyz]

The execution schedule is stored in the database, but the execution history is not tracked, so when the server dies, it forgot its past executions.

The UI for the agent scheduler will soon be available: #8634.

Changes 🏗️

• Entirely removed execution schedule table, replace it with APScheduelr Postgres job store.
• Add more information on the get_execution_schedules API.
• This change decouples the scheduling logic with our application domain, allowing the scheduler backend to easily change in the future as we scale.
• Change the scheduling API routes (/graph/id/schedule --> /schedule, PUT /schedule --> DELETE /schedule).
• Add next_run_time information.
• Allow multiple schedule per graph.

Checklist 📋

For code changes:

• I have clearly listed my changes in the PR description
• I have made a test plan
• I have tested my changes according to the test plan:
  • ...

Example test plan

• 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

For configuration changes:

• .env.example is updated or already compatible with my changes
• docker-compose.yml is updated or already compatible with my changes
• I have included a list of my configuration changes in the PR description (under Changes)

Examples of configuration changes

• Changing ports
• Adding new services that need to communicate with each other
• Secrets or environment variable changes
• New or infrastructure changes such as databases

[qodo-merge-pro]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

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

🧪 PR contains tests

🔒 Security concerns SQL Injection: The database URL is parsed and reconstructed manually in _extract_schema_from_url function. While urlparse is used, the function should validate/sanitize the schema parameter before using it in SQL queries to prevent potential SQL injection.

⚡ Recommended focus areas for review Error Handling The execute_graph function catches all exceptions but only logs them. Consider whether failed jobs should be retried or if errors should trigger notifications. Data Validation No validation is performed on the cron expression before adding jobs. Invalid cron expressions could cause scheduling failures. Type Safety The type checking for inputEntries could be more robust. Consider adding more specific type guards.

[netlify]

✅ Deploy Preview for auto-gpt-docs ready!

Name	Link
🔨 Latest commit	172045f
🔍 Latest deploy log	https://app.netlify.com/sites/auto-gpt-docs/deploys/6735c3367915930008339bdb
😎 Deploy Preview	https://deploy-preview-8649--auto-gpt-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[netlify]

✅ Deploy Preview for auto-gpt-docs canceled.

Name	Link
🔨 Latest commit	7fd3f2d
🔍 Latest deploy log	https://app.netlify.com/sites/auto-gpt-docs/deploys/6737144dd09c8a0008c27b9c

[github-actions]

This pull request has conflicts with the base branch, please resolve those so we can evaluate the pull request.

[github-actions]

Conflicts have been resolved! 🎉 A maintainer will review the pull request shortly.