feat: add Better E2B Sandbox plugin

[LogicOber]

Plugin Submission Form

1. Metadata

• Plugin Author: lysonober
• Plugin Name: Better E2B Sandbox
• Repository URL: https://github.com/LogicOber/dify-plugins/tree/feat/better-e2b-sandbox/LogicOber/better-e2b-sandbox

2. Submission Type

• New plugin submission
• Version update for existing plugin

3. Description

This PR adds a new Dify Tool plugin Better E2B Sandbox (packaged as .difypkg) that lets Dify workflows create and manage E2B cloud sandboxes.

Key capabilities include:

• Create/manage sandboxes (create, connect, pause, resume, kill)
• Claude Code–optimized sandbox setup and interaction
• Next.js scaffolding (npm and Bun) and developer workflow helpers
• Stateful interactive shell sessions (start/send/kill)
• Package installation, file read/write operations, template building, and lifecycle/timeout management helpers (including heartbeat/extend patterns)
• Optional output guarding to reduce accidental secret leakage in workflow outputs

4. Checklist

• I have read and followed the Publish to Dify Marketplace guidelines
• I have read and comply with the Plugin Developer Agreement
• I confirm my plugin works properly on both Dify Community Edition and Cloud Version
• I confirm my plugin has been thoroughly tested for completeness and functionality
• My plugin brings new value to Dify

5. Documentation Checklist

• Step-by-step setup instructions
• Detailed usage instructions
• All required APIs and credentials are clearly listed
• Connection requirements and configuration details
• Link to the repository for the plugin source code

6. Privacy Protection Information

Data Collection

This plugin does not intentionally collect or store end-user personal data.
It processes inputs provided by the workflow (sandbox commands/prompts, file contents, metadata labels) to operate E2B sandboxes and may handle credentials configured by the operator (e.g., E2B/Anthropic/GitHub/Vercel tokens) strictly for sandbox operations.

Privacy Policy

• I confirm that I have prepared and included a privacy policy in my plugin package based on the Plugin Privacy Protection Guidelines