[Feature Request] Run production Docker containers as a non-privileged user

Describe your feature request
Current Dockerfiles (specifically 'docker/deployment.Dockerfile') lack a 'USER' instruction, causing the Typesense server process to run as 'root' by default. Adding a non-privileged user (e.g., 'typesense') and switching to it would align the project with security best practices for containerized applications.

Please describe your use-case for the feature request
Running as a non-root user provides an essential layer of defense-in-depth. In the event of a potential process breakout or container escape vulnerability, having the process restricted to a non-privileged user significantly limits the potential impact on the host system and other containers.

Describe alternatives you've considered
Using a custom entrypoint script to handle user creation and permission management at runtime is an alternative, but a declarative 'USER' instruction in the Dockerfile is generally more transparent and easier for security scanners to validate.

Additional context
Implementation would require ensuring the 'typesense' user has appropriate permissions on data and log volumes. Discussion on whether this should be a breaking change or a new tagged image (e.g., ':latest-nonroot') would be beneficial.

Review docker/deployment.Dockerfile and the data and log volume requirements described in the issue. Determine how the proposed typesense user should access those volumes and whether the change belongs in the existing image or a separate tag. Done means production containers run the server as non-root while retaining required data and log access.