feat(vefaas): add vefaas_cli_sdk module for streamlined deployment and local development

[pamaforce]

Summary

This PR introduces a major refactoring of the veFaaS MCP Server, porting core capabilities from vefaas-cli to Python. The new vefaas_cli_sdk module provides:

• 🚀 Streamlined Deployment: One-command deployment with automatic project detection
• 💻 Local Development Support: Pull function code, auto-generate config files, and sync changes
• ⚙️ Unified Configuration: Compatible with vefaas-cli's .vefaas/config.json format

---

Highlights

🚀 One-Command Deployment

Before (6 tool calls required):

detect_project → create_function → upload_code → release_function → create_vefaas_application → poll_status

After (1 tool call):

deploy_application(project_path="/path/to/app", name="my-app", start_command="...", port=8080)
# Returns: application_id, function_id, access_url, console_url

💻 Local Development Workflow

# 1. Pull existing function code for local development
pull_function_code(function_id="xxx", dest_dir="/path/to/dev")
# → Downloads code, generates vefaas.yaml with function config

# 2. Edit code locally...

# 3. Push changes back (auto-reads config from vefaas.yaml)
update_function(function_id="xxx", project_path="/path/to/dev")
release_function(function_id="xxx")

# Or use one-command deploy with cached config
deploy_application(project_path="/path/to/dev")
# → Auto-reads function_id from .vefaas/config.json

⚙️ Cross-Region Deployment

# Deploy to different region - creates new application
deploy_application(project_path="/path/to/app", name="my-app-sg", region="ap-southeast-1")
# → Ignores cn-beijing config, creates fresh deployment in ap-southeast-1

---

New Module: vefaas_cli_sdk

A new SDK module ported from vefaas-cli (TypeScript):

File	Purpose	Lines
detector.py	Auto-detect framework, runtime, commands	~670
deploy.py	VeFaaSClient, deployment workflow	~1000
config.py	Read/write config files	~270

Supported Frameworks

Node.js: Next.js, Nuxt, Vite, VitePress, Rspress, Express, Astro, SvelteKit, Remix, Angular, Gatsby, CRA

Python: FastAPI, Flask, Streamlit, Django

Static: HTML sites, Hugo, MkDocs, Zola, Hexo

---

Tool Changes

Enhanced Tools

Tool	Changes
deploy_application	PRIMARY TOOL - Full workflow automation, region-aware config, actionable error messages
detect_project	Uses new detector module for accurate framework detection
get_function_detail	Returns source_type, better optional field handling
pull_function_code	Generates vefaas.yaml for local dev, graceful error handling
update_function	Uses .vefaasignore filtering for code packaging

Removed Tools (Merged into deploy_application)

• create_vefaas_application
• poll_vefaas_application_status
• list_vefaas_application_templates
• get_vefaas_application_template

---

Key Features

1. Region-Aware Configuration

Config IDs are only used when the stored region matches the target region:

# .vefaas/config.json
{"function": {"id": "xxx", "region": "cn-beijing"}}

# deploy_application(region="cn-shanghai") 
# → Ignores cn-beijing config, creates new deployment

2. Dual Config Format Support

Writes to both formats for compatibility:

• .vefaas/config.json - vefaas-cli format
• vefaas.yaml - Legacy MCP format

3. .vefaasignore Support

Package code with gitignore-style patterns:

# Auto-created .vefaasignore
.git/
.venv/
__pycache__/
node_modules/
.vefaas/

4. Actionable Error Messages

{
  "success": false,
  "error": "build_command is required for Node.js project",
  "next_action": "Provide build_command or set skip_build=True"
}

---

File Changes

File	Change
vefaas_cli_sdk/__init__.py	🆕 New
vefaas_cli_sdk/deploy.py	🆕 New (~1000 lines)
vefaas_cli_sdk/detector.py	🆕 New (~670 lines)
vefaas_cli_sdk/config.py	🆕 New (~270 lines)
vefaas_server.py	✏️ Refactored
vefaas_server_test.py	✏️ Updated tests
pyproject.toml	✏️ Added dependencies

---

New Dependencies

• pathspec - .vefaasignore pattern matching
• pyyaml - YAML config file support

---

Testing

• Unit tests for vefaas_cli_sdk module
• Region-aware deployment tests
• Cross-region deployment scenarios
• Config file compatibility tests

[CLAassistant]

All committers have signed the CLA.