fix(platform): Fix containerized connection issues with DB Manager

[aarushik93]

Background

In this PR #8283, a change was added so that the rest service also communicates with the DB manager, which was not previously the case.
In docker and k8s environments the host is handled by their respective environments, so the DB host needs to be specified as it's not on the same host.

Changes 🏗️

Added DBMANAGER_HOST to docker compose and server values.dev.yaml and values.prod.yaml

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 Configuration Update Verify that the added DBMANAGER_HOST environment variable is correctly set to 'executor' and that this value is appropriate for the containerized environment. Environment Configuration Ensure that the DBMANAGER_HOST value is correctly set to "autogpt-server-executor.dev-agpt.svc.cluster.local" and that this hostname is valid in the development environment. Production Configuration Confirm that the DBMANAGER_HOST value "autogpt-server-executor.prod-agpt.svc.cluster.local" is correct for the production environment and that it aligns with the actual infrastructure setup.