feat(gateway): add tools_include and tools_exclude filters

[ecthelion77]

✨ Feature / Enhancement PR

🔗 Epic / Issue

Closes #4021

---

🚀 Summary (1-2 sentences)

Add optional tools_include and tools_exclude fields to gateways that filter which tools are imported from a remote MCP server using fnmatch glob patterns.

---

🧪 Checks

• make lint passes (ruff + black)
• make test passes
• CHANGELOG updated (if user-facing)

---

📓 Notes

Use case

When connecting to a single MCP backend that exposes many tools (e.g. an ITSM API with 40+ endpoints), it is often useful to split it into multiple gateways with different tool subsets and different auth schemes:

• Gateway A: all tools except project management (tools_exclude: ["*project*"]) — OAuth auth
• Gateway B: only project management tools (tools_include: ["*project*"]) — API key auth

Filtering logic

1. If tools_include is set, only tools whose name matches at least one include pattern are kept
2. If tools_exclude is set, tools matching any exclude pattern are removed
3. When both are set, include is applied first, then exclude
4. Empty/null means no filtering

Patterns use Python fnmatch syntax (*project*, manage-ticket*).

Changes

File	Change
db.py	tools_include/tools_exclude JSON columns on Gateway
schemas.py	Fields on GatewayCreate, GatewayUpdate, GatewayRead
gateway_service.py	_apply_tool_filters() + 4 call sites (refresh, register, update, activate)
export_service.py	Export support
import_service.py	Import support
admin.py	Form parsing in create/edit flows
formSubmitHandlers.js	Comma→JSON array conversion
gateways.js	Edit modal population
admin.html	Input fields in create + edit forms
Alembic migration	New columns (IF NOT EXISTS guard)

[ecthelion77]

Suggested labels: enhancement, python, api