feat(blocks/nvidia): Add Nvidia deepfake detection block

[aarushik93]

Adding a block to allow users to detect deepfakes in their workflows.
This block takes in an image as input and returns the probability of it being a deepfake as well as the bounding boxes around the image.

Changes 🏗️

• Added NvidiaDeepfakeDetectBlock
• Added the ability to upload images on the frontend
• Added the ability to render base64 encoded images on the frontend

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	0762389
🔍 Latest deploy log	https://app.netlify.com/sites/auto-gpt-docs-dev/deploys/677d46e087b6600008652a50

[netlify]

✅ Deploy Preview for auto-gpt-docs canceled.

Name	Link
🔨 Latest commit	0762389
🔍 Latest deploy log	https://app.netlify.com/sites/auto-gpt-docs/deploys/677d46e09d4cb30008a6796b

[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 code exposes the Nvidia API key in the request headers. While it uses SecretStr for storage, the key is exposed in plaintext when making the API request. Consider using a more secure way to handle the API key, such as passing it through a secure proxy or using environment variables.

⚡ Recommended focus areas for review Error Handling The error handling in the run method could be improved. Currently it catches all exceptions generically and sets status to ERROR without distinguishing between different error types (API errors, network issues, etc). except Exception as e: yield "error", str(e) yield "status", "ERROR" yield "is_deepfake", 0.0 yield "image", "" File Validation The image file validation is minimal, only checking if file type starts with 'image/'. Consider adding size limits and more specific file type validation. if (!file.type.startsWith("image/")) { console.error("Please upload an image file"); return; }