feat(blocks): Add Exa API Blocks

[aarushik93]

Adding Exa API blocks because it does very cool search and web scrapping

Changes 🏗️

Adding Exa API blocks:
Search

Added a new calendar and time input

Added _auth.py for Exa API too.

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-dev canceled.

Name	Link
🔨 Latest commit	26fb5ea
🔍 Latest deploy log	https://app.netlify.com/sites/auto-gpt-docs-dev/deploys/674db22aecdf7b0008459941

[netlify]

✅ Deploy Preview for auto-gpt-docs ready!

Name	Link
🔨 Latest commit	26fb5ea
🔍 Latest deploy log	https://app.netlify.com/sites/auto-gpt-docs/deploys/674db22a9549c300085e75a2
😎 Deploy Preview	https://deploy-preview-8835--auto-gpt-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[github-actions]

This pull request has conflicts with the base branch, please resolve those so we can evaluate the pull request.

[github-actions]

Conflicts have been resolved! 🎉 A maintainer will review the pull request shortly.

[qodo-merge-pro]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

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

🧪 No relevant tests

🔒 Security concerns API Key Exposure: The Exa API key is sent in request headers. While using HTTPS, ensure the requests are not logged or cached in a way that could expose the API key. Also verify that error responses don't include the API key in error messages or logs.

⚡ Recommended focus areas for review Error Handling The error handling in the search block is too generic and may hide important error details. Consider handling specific error types separately and providing more informative error messages. Input Validation The block accepts several datetime fields but there's no validation to ensure end dates are after start dates, or that dates are within reasonable ranges. State Management The time input state is managed separately from the date state which could lead to synchronization issues. Consider combining them into a single state.

[aarushik93]

jsonschema converts data time to type string with format date-time