feat(platform): Add Gmail and Google Sheets blocks + fix Google OAuth

[ntindle]

Background

We have several agents that we want to integrate with google services

Changes 🏗️

This pr does a handful of things

OAuth

• Adds oauth scopes to the oauth base
• adds default scopes to the oauth base
• adds upgrading scopes to google
• adds helpers for scopes

Blocks

• Adds gmail read/write blocks
• Adds google sheets read/write block
• Adds a few more categories for these blocks (up for discussion)

Testing 🔍

Warning

This PR has auth changes. Review it top to bottom. Test plan included in comments, with issues that I've seen highlighted

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

[netlify]

✅ Deploy Preview for auto-gpt-docs canceled.

Name	Link
🔨 Latest commit	08ffc25
🔍 Latest deploy log	https://app.netlify.com/sites/auto-gpt-docs/deploys/66fec64fc08c5e00084d716b

[ntindle]

guess is most of the frontend stuff isn't needed

[ntindle]

Test Plan

test logging in/out and making sure your tokens for github and google still work

Test gihtub agents

test showing status and output of blocks during execution

test /monitoring post requests -> sometimes failed for me due to being 'too big'. Is this known

Test sheets reading/writing -> can you do the same sheet with a list input etc

Test reading/sending emails -> don't get us rate limited or blocked with spam while testing this. Seriously. Only email internal accounts, or yourself.

[qodo-merge-pro]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

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

🧪 No relevant tests

🔒 Security concerns Sensitive information exposure: The OAuth flow involves handling sensitive information such as access tokens and refresh tokens. While the code appears to use SecretStr for storing these tokens, extra care should be taken to ensure they are not logged or exposed in any way, especially in error messages or debug logs.

⚡ Recommended focus areas for review Error Handling The exchange_code_for_tokens method has complex error handling that might benefit from refactoring for better readability and maintainability. Error Logging The callback function has multiple try-except blocks that might be consolidated for better error handling and logging. Complex Function The handleOAuthLogin function is quite long and complex. Consider breaking it down into smaller, more manageable functions.

Stale

[Pwuts]

not sure how this passed CI when OAuthState has no scopes field

[Pwuts]

apparently we're not running CI on autogpt_libs