A wake of a sandbox moving to another server returns 409 sandbox_moving; terminals reattach without errors

A wake, or a call that wakes a paused sandbox, while the sandbox's paused memory and disk are still being copied to another server now returns 409 sandbox_moving with Retry-After, instead of 503 no_capacity. The sandbox is unchanged and stays paused. The JavaScript, Python, Go, Java and Ruby SDKs wait and retry it as they do no_capacity. A terminal opened with processId on a shell that another terminal already typed into no longer closes with 502 guest_failed ("invalid input offset") on its first keystroke. Its input now starts where the shell's input is.