docker apiserver doesn't come back up if container restarted

**What happened**:

While testing eksa in docker for fun, I restarted the container containing the apiserver.

"command failed" err="open /etc/kubernetes/pki/apiserver.crt: no such file or directory"

/etc/kubernetes/pki/apiserver.crt and /etc/kubernetes/pki/apiserver.key are now missing.

**What you expected to happen**:

apiserver to come back up.

**How to reproduce it (as minimally and precisely as possible)**:

docker stop mgmt-server && docker start mgmt-server

**Anything else we need to know?**:

Just don't understand where the apiserver certs are going. I get the docker deploy is for testing but odd I can't get the apiserver back.

**Environment**:
- EKS Anywhere Release:

eksctl anywhere version
Version: v0.22.4
Release Manifest URL: https://anywhere-assets.eks.amazonaws.com/releases/eks-a/manifest.yaml
Bundle Manifest URL: https://anywhere-assets.eks.amazonaws.com/releases/bundles/97/manifest.yaml

Reproduce the failure with `docker stop mgmt-server && docker start mgmt-server`, then investigate how the Docker deployment creates or preserves `/etc/kubernetes/pki/apiserver.crt` and `apiserver.key`. Done means the apiserver starts successfully after the container is restarted and both certificate files remain available.

Written by the indexing model from the issue text.