When a deployment is soft-deleted, it should be immediately removed from
all ranking systems to ensure ranking data reflects only active deployments.

Changes:
- Remove deployment from deploymentRanker when soft-deleted
- Update namespace ranker by subtracting the deployment's risk score
- Update cluster ranker by subtracting the deployment's risk score

This ensures consistency with query filtering (which excludes deleted
deployments) and prevents ranking data from including stale deployments.

User request: "should soft deleted deployments be immediately removed
from the deploymentranker?"

Why: Namespace and cluster rankers were not being updated when deployments
were soft-deleted, leading to incorrect aggregate risk scores that included
deleted deployments. The deployment ranker also retained entries for
soft-deleted deployments despite them being filtered from all queries.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

Changed the GraphQL deployment loader's CountAll method to count
deployments across all states (active and soft-deleted) instead of
only active deployments.

Rationale: The name "CountAll" semantically implies counting everything,
while CountFromQuery is available for filtered counts. This makes the
API more intuitive:
- CountAll() → all deployments regardless of state
- CountFromQuery(query) → filtered deployments (can include active filter)

Note: CountAll is currently unused in the codebase but is part of the
common loader interface pattern. If it's ever used in the future, it
will now return the total count across all states as the name implies.

User request: "let CountAll actually count all deployments of all
states - including soft deleted ones."

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>