[bitnami/discourse] Fix sidekiq volume mount in docker compose (#79078)

* Fix sidekiq volume mount in docker compose

In 2.4.4-debian-10-r8 release, a change was made noted in the readme that says:

> Discourse and Sidekiq now make use of the same volume to persist data. This solves issues related to being unable to locate some files generated on-demand by the Sidekiq job scheduler.

This change applies this same volume to the docker-compose file. Without the change, sidekiq stalls indefinitely at startup waiting for the discourse DB to be populated. This fixes issues e.g. as noted in #52988

Signed-off-by: Nick Touran <contact@partofthething.com>

* Removed unused sideqik volume

Signed-off-by: Nick Touran <contact@partofthething.com>

---------

Signed-off-by: Nick Touran <contact@partofthething.com>

bitnami/discourse/docker-compose.yml

@@ -45,7 +45,7 @@ services:
     depends_on:
       - discourse
     volumes:
-      - 'sidekiq_data:/bitnami/discourse'
+      - 'discourse_data:/bitnami/discourse'
     command: /opt/bitnami/scripts/discourse-sidekiq/run.sh
     environment:
       # ALLOW_EMPTY_PASSWORD is recommended only for development.
@@ -64,5 +64,3 @@ volumes:
     driver: local
   discourse_data:
     driver: local
-  sidekiq_data:
-    driver: local