Make AWS S3 bucket name fully configurable

Describe the issue
Currently, the AWS S3 bucket name is constructed dynamically in code like this:

return f"{self.AWS_S3_BUCKET_PREFIX}-{self.ENVIRONMENT}"

• This assumes that all bucket names will follow the - pattern.

• However, in future scenarios, users or organizations might bring their own bucket names, which may not include the environment in their naming convention or may follow completely different patterns.

• Hardcoding the bucket name composition like this makes it inflexible and prone to failure if the naming convention does not match.

Expected behavior

• There should be a single, fully-configurable AWS S3 bucket name setting(e.g., AWS_S3_BUCKET_NAME)which is used directly without concatenating prefix and environment in code.

• This allows using existing customer buckets regardless of naming convention.

Recherchez dans le backend la construction du bucket basée sur AWS_S3_BUCKET_PREFIX et ENVIRONMENT présentée dans l’issue, puis suivez l’endroit où le paramètre du bucket est lu. Remplacez cette composition par un seul paramètre configurable de nom de bucket et vérifiez que le nom configuré est utilisé tel quel, y compris pour les noms sans suffixe d’environnement.