Change RedpandaContainer startup script path

Hi,

we're running Testcontainers in Openshift using Kubedock; when using RedpandaContainer, our tests break because , after the container is started, the actual startup script is copied to / which is not writable by the redpanda user. I think we could safely switch to another directory, for example /var/lib/redpanda (btw I see other libraries are doing the same, see here).
I realize we have a pretty unique setup but the change should be pretty simple and probably using a directory owned by the user that runs the container could prevent issues in other environments too.
If you think it's feasible I can work on a PR.

Thanks,

lorenzo

Comienza localizando la implementación de RedpandaContainer e inspecciona dónde se copia su script de inicio después de que se inicia el contenedor. Comprueba el comportamiento existente del contenedor en la configuración de OpenShift y Kubedock descrita en el issue. Se considera terminado cuando el script se coloca en un directorio en el que el usuario redpanda pueda escribir y las pruebas afectadas dejan de fallar.