fix(backend): Fix DatabaseManager usage by calling it on-demand

[majdyz]

Background

We unintentionally cached the DatabaseManager connection object and shared it across different threads in SupabaseIntegrationCredentialsStore

Changes 🏗️

• Make DatabaseManager connection acquisition on the fly and cache it within the class.
• Remove the need to provide a port number for connecting to pyro service (inferred from the class).
• Moved utils/cache.py to autogptlib.

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 Thread Safety The use of thread_cached_property for db_manager might lead to thread safety issues if not properly handled. Ensure that the DatabaseManager client is thread-safe. Error Handling The removal of the db_manager parameter from IntegrationCredentialsManager initialization might lead to unexpected behavior if the database connection is not properly established elsewhere. Code Duplication The get_host and get_port methods are implemented in multiple places. Consider creating a base class or utility function to reduce duplication.