fix(runtime): close callback admission during shutdown
Hard-killing an in-process silo can deadlock host disposal when stateless workers have transaction calls in flight.
The CI dumps show host disposal waiting on StatelessWorkerGrainContext.DisposeAsyncInternal. Faulting the original callbacks resumes transaction cleanup, which can issue follow-up requests after the shutdown sweep and register callbacks that can never receive responses.
Close callback admission before draining outstanding calls in both silo and client runtimes. Requests check the stopping state before insertion and again afterward, ensuring each callback is completed by either the shutdown sweep or the admitting thread. Callback cancellation registration now uses a nonblocking publication/disposal handshake so synchronous cancellation or concurrent completion cannot leak a registration.
The regression coverage includes multiple blocked silo workers which retry after shutdown, a client call which retries after shutdown, cancellation during registration, and registration attempted after callback completion.