Add a container image for the server

Why: the server is a single static binary with no dependencies, so its
container should be nothing but that binary. Shipping one also makes the
master key easy to lose, which needed handling rather than documenting.

What:
- Dockerfile: two stages, runtime is scratch plus the binary and a CA bundle
  for reaching an OIDC provider, running as uid 65532. About 9 MB. The build
  stage copies only go.mod, cmd/keeporgd and internal, so client or docs
  changes do not invalidate it.
- The image has no shell, so HEALTHCHECK runs `keeporgd -healthcheck`, a new
  flag that probes /healthz on the configured address and exits non-zero
  with a reason. podman needs --format docker to keep the healthcheck at
  all, which the Makefile passes when it picks podman.
- New -master-key-file flag, so a mounted secret works without a config file.
- The server now checks at startup whether the master key still opens the
  stored vault keys, and says so. Without it, a container restarted without
  its key discovers the problem one failed merge at a time.
- make docker, docker-run and docker-save; a compose example with read_only,
  cap_drop ALL and no-new-privileges.
- The client and the server now version independently, so their Debian
  changelogs are split per package and `make changelog` takes PKG=.
  Server 0.3.0; the clients stay at 0.2.0.

Proved: built with podman and run. The container serves /healthz and /web,
its own healthcheck reports healthy, and a vault created through it was
edited from the same base by keepassxc-cli twice, merged by the server into
version 3, and read back with both entries intact. Restarted without the
master key it warns "1 of 1 stored vault keys do not open with this master
key" and answers a merging push with 409 merge_failed, leaving the vault
untouched; restored, it logs "1 vault keys available for merging" and merges
again. The same key supplied through -master-key-file from a mounted file
works identically. Both .deb packages build with their own changelog, and
make check is clean.

internal/server/server.go

@@ -99,10 +99,45 @@ func New(cfg Config, lg *log.Logger) (*Server, error) {
 	if cfg.OIDC.Enabled() {
 		s.oidc = newOIDCProvider(cfg.OIDC, cfg.ExternalURL+"/oidc/callback")
 	}
+	s.checkVaultKeys()
 	s.routes()
 	return s, nil
 }
 
+// checkVaultKeys reports at startup whether the master key still opens the
+// vault keys in the state document. Getting this wrong is quiet and
+// expensive: a container started without its master key mounted mints a new
+// one, and every merge then fails one push at a time. Saying so once, at
+// startup, is the difference between a puzzle and a fixable mistake.
+func (s *Server) checkVaultKeys() {
+	var total, broken int
+	s.st.Read(func(st *store.State) {
+		for id, d := range st.Databases {
+			if d.WrappedKey == "" {
+				continue
+			}
+			total++
+			if s.keyring == nil {
+				broken++
+				continue
+			}
+			if _, err := s.keyring.Unwrap(id, d.WrappedKey); err != nil {
+				broken++
+			}
+		}
+	})
+	switch {
+	case broken == 0 && total > 0:
+		s.log.Printf("%d vault keys available for merging", total)
+	case broken > 0:
+		s.log.Printf("WARNING: %d of %d stored vault keys do not open with this "+
+			"master key. Those vaults cannot be merged until the original key is "+
+			"restored (%s or %s). Nothing is lost: clients still open the vaults "+
+			"with their own passwords.",
+			broken, total, secret.MasterKeyEnv, s.cfg.MasterKeyFile)
+	}
+}
+
 // Store exposes the metadata store for bootstrap commands.
 func (s *Server) Store() *store.Store { return s.st }