fix(seaweedfs): fix S3 auth ConfigMap mount reference

[alex-mabrouk]

Description

Fix the SeaweedFS S3 auth ConfigMap reference used by the main Helm chart.

The SeaweedFS package was mounting an auth ConfigMap named:
<release>-auth-config-seaweedfs-auth-config

However, the seaweedfs-auth-config Helm chart actually creates the ConfigMap as: <release>-auth-config

As a result, the S3 pod referenced a non-existent ConfigMap, causing:

• FailedMount errors on the S3 pod
• S3 pod stuck in ContainerCreating
• SeaweedFS release never reaching READY

This change updates the ConfigMap reference to use the actual resource name generated by the auth module.

Related Issue

Fixes #16

Type of Change

• Bug fix
• New feature
• Documentation update
• Refactor / chore
• Breaking change

How to Test

1. Deploy a SeaweedFS release (e.g. seaweedfs or demo-seaweedfs) using package version 4.17.0-p1.
2. Wait for both the auth-config and main HelmReleases to reconcile.
3. Verify that the generated ConfigMap exists:
   kubectl -n <namespace> get cm

Expected:
<release>-auth-config

4. Verify that the S3 pod starts successfully:

kubectl -n <namespace> get pods

5. Confirm that all SeaweedFS components (master, volume, filer, s3) reach Running and the KuboCD Release becomes READY.

Checklist

• I have tested my changes
• Documentation updated if needed
• If breaking change: migration path described above
• I hereby declare this contribution to be licensed under the Apache License Version 2.0.
• I hereby agree to grant TOSIT a copyright license to use my contributions.