fix: handle provider status default cases across providers.

[garvitssoni]

Problem

Across several providers, unknown/transient status values were being coerced into concrete lifecycle states (commonly pending). During deletion this led to incorrect “Starting/Deploying” signals and contributed to UI status regressions.

Root cause

Default-case handling in provider status mappers treated unknown values as known states instead of surfacing “unknown.”

Fix

• Standardize provider mappers to return “unknown” (empty/unset lifecycle) for unrecognized provider status values, rather than defaulting to pending/failed.