feat(blocks): Add Hubspot blocks

[aarushik93]

This PR adds the first few Hubspot blocks so we can create real sales and marketing agents.

Changes 🏗️

Added Hubspot blocks;

• Aded auth for hubspot
• Added Company block
• Added Contact block
• Added Engagement block

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

[netlify]

✅ Deploy Preview for auto-gpt-docs canceled.

Name	Link
🔨 Latest commit	b84dda7
🔍 Latest deploy log	https://app.netlify.com/sites/auto-gpt-docs/deploys/67478beb790a6d00083b0cb7

[netlify]

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

Name	Link
🔨 Latest commit	b84dda7
🔍 Latest deploy log	https://app.netlify.com/sites/auto-gpt-docs-dev/deploys/67478bebf6938d000899d610

[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 API Key Exposure: The API key is being passed in request headers without any additional encryption or security measures. While using HTTPS provides transport security, consider adding rate limiting and request validation to prevent potential abuse of the API key.

⚡ Recommended focus areas for review Error Handling The block lacks proper error handling for API requests. Failed requests could raise exceptions that are not caught and handled gracefully. Hardcoded Value The hubspot_owner_id is hardcoded to "1" in the email sending logic. This should be configurable through the input schema. Data Validation The contact_data and email inputs lack validation for required fields and format before making API calls.

[Pwuts]

These were alphabetically sorted lists, which helps a lot to avoid merge conflicts. Please keep this in mind in the future.

[Pwuts]

Why aren't these separate blocks?

[aarushik93]

They don't need to be seperate blocks. I plan to update the user experience though later to show and hide inputs based on what event is being done.

[Pwuts]

I'm not familiar with Hubspot, but they seem two non-overlapping operations to me. So why are they in one block? The same goes for the HubspotCompanyBlock and HubspotContactBlock, which both support create/update/get operations with non-overlapping implementations.

Merging these in one block is a break of pattern regarding how we implement blocks.

It's important to get it right from the start because we currently don't have a way to make functional changes to blocks without breaking graphs where they are in use.