Fix sushy-tools container startup failures

Resolves issues preventing sushy-tools BMC emulator from starting:
- Fix SSH volume mount path (/root/ssh -> /root/.ssh)
- Explicitly specify config file in container command
- Add SELinux labels (:z) to volume mounts for permission access

These fixes ensure sushy-tools starts correctly and passes health checks
for Redfish endpoint accessibility.

Author: eliorerz

scripts/cleanup.sh

@@ -285,7 +285,7 @@ if [ ${#CLUSTER_POOL_PATHS[@]} -gt 0 ]; then
             for cluster_path in "${CLUSTER_POOL_PATHS[@]}"; do
                 if [ "$POOL_PATH_CHECK" = "$cluster_path" ]; then
                     # Check if not already in the list
-                    if [[ ! " ${POOLS_TO_CLEAN[*]} " =~ " $pool " ]]; then
+                    if [[ ! " ${POOLS_TO_CLEAN[*]} " =~ \ $pool\  ]]; then
                         info "Found pool '$pool' pointing to cluster path $cluster_path, will clean it up"
                         POOLS_TO_CLEAN+=("$pool")
                     fi

scripts/start_sushy_tools.sh

@@ -172,10 +172,11 @@ sudo podman run -d \
     --net host \
     --privileged \
     --name "$CONTAINER_NAME" \
-    -v "$SUSHY_DIR:/root/sushy" \
-    -v "/root/.ssh:/root/ssh" \
-    -v "/var/run/libvirt:/var/run/libvirt" \
-    "${SUSHY_TOOLS_IMAGE}"
+    -v "$SUSHY_DIR:/root/sushy:z" \
+    -v "/root/.ssh:/root/.ssh:ro,z" \
+    -v "/var/run/libvirt:/var/run/libvirt:z" \
+    "${SUSHY_TOOLS_IMAGE}" \
+    sushy-emulator --config /root/sushy/conf.py
 
 # Open firewall port for sushy-tools
 info "Configuring firewall to allow sushy-tools traffic..."