fix(runtime): publish local shutdown membership state
MembershipTableManager maintained local status separately from published membership snapshots, allowing local state to diverge and treating intentional shutdown transitions as fatal membership failures.
This change atomically publishes each membership snapshot together with the local silo status derived from it. It also records lifecycle stop entry so Dead transitions during an intentional shutdown do not invoke fatal termination, while preserving fatal handling for unexpected Dead transitions. When a newer incarnation is detected, the silo now persists its Dead status before self-termination.
Keeping snapshot and local status in one published state makes membership decisions consistent and gives shutdown paths a clear distinction from unexpected membership death.