Service Discovery for Tenant-Manager

Scans the current project and produces a visual report of the Service → Module → Resource hierarchy. This report tells you exactly what needs to be registered in the dispatch layer (pool-manager) to provision tenants for this service.

How It Works

The dispatch layer has three entities that must be registered before provisioning tenants:

1. Service — the application (e.g., "ledger", "plugin-crm"). Has a type: product or plugin.
2. Module — a logical grouping within the service (e.g., "onboarding", "transaction"). Each module gets its own database pool per tenant.
3. Resource — infrastructure a module needs: postgresql, mongodb, or rabbitmq. Each resource gets provisioned per tenant per module.

Redis is not a dispatch layer resource — it uses key prefixing via GetKeyContext and does not need registration.

Phase 1: Service Detection