`install` run again with the other --server now moves the mail server,
with its configuration and mail, instead of refusing ("not built yet").
- Needs an API key (--key - / INBUXA_API_KEY, never written down), as
certs and join do: the server's listeners (jmap.HostListeners, and the
new ContainerListeners) and its auto-ban exemptions change with the
shape, and only the server changes those.
- beginMove checks the key, stops what runs here and archives the data
into <dir>/backups before anything of the new shape is written; finish
copies it (renamed into place, or streamed into the volumes), rewrites
the one path config.json names, starts the server in its new shape --
on the host first behind the loopback fence (modeFenced) until its
listeners are fitted -- and checks it came back configured.
- Copied, never moved: the volumes, or <dir>/server, stay where they were.
Leftovers of an earlier install in the target are archived and emptied,
never mixed in. A failure in finish, or anything stopping the run
before it (abort), puts the old shape back.
- The plan says when a run is a move. `apply -f` moves too.
e2e/cases/move-server.sh: 56/56 (no key and a wrong key change nothing;
a broken host binary puts the container back; container -> host -> container
keeping an account and IMAP sign-in, front ends answering, status agreeing).
install-host.sh expects the key refusal in place of "not built yet": 44/44;
uninstall-host 14/14, rerun-host-server 12/12.