Preserve generic post-deploy failure evidence

[shiny-code-bot]

Summary

• convert unexpected generic post-deploy hook exceptions into failed post-deploy evidence instead of escaping without records
• persist runtime identity and refreshed inventory when the provider deploy succeeds but post-deploy fails
• update generic deploy tests for ClickException, unexpected exception, and returned failed evidence paths

Validation

• uv run python -m unittest tests.test_generic_web_deploy tests.test_generic_web_rollback tests.test_service
• uv run --extra dev ruff check --diff control_plane/workflows/generic_web_deploy.py tests/test_generic_web_deploy.py
• uv run --extra dev ruff check control_plane/workflows/generic_web_deploy.py tests/test_generic_web_deploy.py
• uv run --extra dev ruff format --check control_plane/workflows/generic_web_deploy.py tests/test_generic_web_deploy.py
• uv run --extra dev mypy control_plane tests
• uv run python -m unittest

Inspection note

JetBrains changed-file inspection was retried twice. It extracted zero problems both times, but the inspection capture did not settle before the tool deadline and returned STATUS: capture_incomplete.