Worker cache handover

Is your feature request related to a problem? Please describe.
When histories are large, a worker restart invalidates all the cached histories. This leads to increased latency for all the workflows that were cached on that worker.

Describe the solution you'd like
When a worker gracefully shuts down (or even crashes), the workflows that are cached on it are recovered on other workers to get cached before any tasks are generated for them.

Additional context
This is how a user requested it:

Moving workflows that have a high history size from one worker to another when you have to kill the worker (to update for example) can be painful. It would be great if there was a way to mark workflows as "require preemptive cache alocation" or something that ensures that the cache is coordinated when killing the worker (or some similar strategy to make killing such a worker less painful)

Start by identifying the worker shutdown, workflow cache ownership, and cache recovery entry points in the repository. Define how cached workflows move after graceful shutdown or a crash, and how recovery must complete before new tasks are generated; done should include tests covering worker handover and cache restoration.