Feature request: Kubernetes-specific container

Some suggestions from a customer which might work well if we had a Kubernetes-specific version of the Matomo docker container:

> The container as produced is almost friendly for running with no PVC at all, enabling cheaper and more effective scaling. If the config data was moved to the database and it could operate without it entirely by just environment variables to reach it, it'd be able to operate better in a kubernetes context.

> In a common kubernetes environment, the ingress routing can likely be handled by an ingress, removing the need to have apache in the container.

Start by reviewing the repository's current Docker container configuration and how it handles persistent configuration, database connectivity, and Apache. Compare those assumptions with the Kubernetes-specific suggestions in the issue. Done would require an agreed, concrete scope for PVC-free operation and ingress-based routing; no files or tests are named.

Written by the indexing model from the issue text.