feat(services): add status filter to service list endpoint

[dennisonbertram]

Problem

Deployment-history Story 13 (Viewing Deployment Status Across Multiple Services) describes filtering services by status: "Response includes 10 services with statuses: 'running', 'deploying', 'stopped', 'crashed', 'failed'. She identifies 2 services that need redeploy." Currently, the list endpoint only supports limit and offset — users must fetch all services and filter client-side.

Expected Behavior

• GET /v1/services?status=crashed — filter by status
• GET /v1/services?status=crashed,failed — filter by multiple statuses
• Useful for batch operations (e.g., "redeploy all crashed services")

Context

Discovered via UX Paths analysis (docs/ux-paths/topics/deployment-history.md — Story 13)

[dennisonbertram]

Needs clarification: What statuses should be filterable? Just the main ones (running, stopped, failed, crashed, deploying) or also circuit breaker states? Should this be a single ?status=running parameter or support multiple values like ?status=running,stopped?

[dennisonbertram]

PR created: #140