Move Devnet to separate package #60
Description
Problem
The Devnet functionality currently in @evolution-sdk/evolution imports Node.js-specific dependencies (dockerode) that cause issues when importing the SDK in browser/client environments like Next.js.
Solution
Create a new @evolution-sdk/devnet package that:
- Contains all Devnet-related code (Devnet.ts, DevnetDefault.ts)
- Depends on dockerode and other Node.js-only libraries
- Can be used independently: `import { Devnet } from '@evolution-sdk/devnet'`
This allows @evolution-sdk/evolution to be fully client-safe while keeping Devnet functionality available for those who need it.
Impact
- Fixes Next.js client component imports
- Separates concerns (client-safe SDK vs server-only tools)
- Maintains backward compatibility (users add devnet package separately)
- All existing tests continue to pass