feat(backend/executor): Add TERMINATED execution status

[Pwuts]

• Resolves Implement "STOPPED" graph execution status #9182

Formerly known as FAILED with error message TERMINATED.

Changes 🏗️

• Add TERMINATED to AgentExecutionStatus enum in DB schema (and its mirror in the front end)
• Update executor to give terminated node and graph executions status TERMINATED instead of FAILED/COMPLETED
• Add TERMINATED case to status checks referencing AgentExecutionStatus

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:
  • Start and forcefully stop a graph execution

[netlify]

✅ Deploy Preview for auto-gpt-docs-dev canceled.

Name	Link
🔨 Latest commit	bfdaac9
🔍 Latest deploy log	https://app.netlify.com/sites/auto-gpt-docs-dev/deploys/677c5c0bd73967000880aafd

[netlify]

✅ Deploy Preview for auto-gpt-docs canceled.

Name	Link
🔨 Latest commit	bfdaac9
🔍 Latest deploy log	https://app.netlify.com/sites/auto-gpt-docs/deploys/677c5c0b3d1d730008f8aa90

[majdyz]

Looks good,
Will this part of the code also capture the TERMINATED signal?
https://github.com/Significant-Gravitas/AutoGPT/pull/9185/files#diff-1b278ebf10a9da0fb5030010222b3a6df2b05a5463cad428cd6c38a1541b0f73R204-R220

If yes then it could be the terminated status is overridden? if not then it's all good :)

[Pwuts]

Will this part of the code also capture the TERMINATED signal?
#9185 (files)

If yes then it could be the terminated status is overridden? if not then it's all good :)

I was having such an issue at first, which is why I did this:
8c80ed8

I tested it and now it works. :)