fix: strip provider-incompatible email patterns

[fudujiji]

Fixes #45.

Summary

• strip the generated email lookaround regex from MCP tool schemas
• keep z.string().email() validation for affected email fields
• add a tools/list regression test for provider-incompatible regex lookarounds

Why

OpenAI's tool schema validator and Anthropic Sonnet strict mode reject regex lookarounds in tool input schemas. The generated Dokploy tools currently emit the same lookaround email pattern for Bitbucket, domain, user, and organization email fields, which prevents strict clients from accepting the tool list.

This keeps the server-side API validation unchanged and only removes the provider-incompatible generated schema pattern.

Verification

• npx --yes pnpm@10.24.0 generate
• npx --yes pnpm@10.24.0 test -- src/server.test.ts
• npx --yes pnpm@10.24.0 type-check
• npx --yes pnpm@10.24.0 lint
• npx --yes pnpm@10.24.0 build
• git diff --check