Docker compose postgres volume update

Currently the docker-compose-dev.yml file defines the postgres volume as the following:

    volumes:
      - ./docker-dev-volumes/postgresql/data:/var/lib/postgresql/data

https://github.com/IQSS/dataverse/blob/b15b89f794415662ed860178c8f857446477d7b9/docker-compose-dev.yml#L79C5-L80C70

I was not able to get the Docker container for postgres to run with this setting. It was throwing errors about setting permissions for /var/lib/postgresql/data. I'm thinking the better approach would be to use a volume of - ./init.sql:/docker-entrypoint-initdb.d/init.sql or similar since you should not need to worry about permissions. The docker-entrypoint-initdb.d is the default initialization point for postgres in Docker https://hub.docker.com/_/postgres/. This will be useful when creating Docker compose instances for testing things such as an API call to update an existing file, where you want a preconfigured database and data as a starting point.

Anyway, just making this a placeholder for discussion and a pull request.

Inspect the postgres service and volume definition in docker-compose-dev.yml, then reproduce the reported permission error by starting the development Compose setup. Compare the current data-volume approach with the proposed docker-entrypoint-initdb.d/init.sql approach using the Postgres image documentation. Done means the container starts without the permission error and supports the intended preconfigured database setup.