Add details to why the minio tenant headless service must be used over the normal clusterIP service

["The console service is for managing the tenant, while the hl service exposes the S3 compatible API. "](https://cloudnative-pg.io/plugin-barman-cloud/docs/object_stores/#minio-object-store)

the `-hl` service is a headless service. There is also a `minio` "normal" (clusterIP) service created. Why can't we used the "normal" service? Does the plugin have to connect to all of the pods behind the service? I have been testing with a single pod and it works with the normal service (not the headless version) but that may just be because there is a single pod. Can you update the docs to say why it can't use the normal service, if indeed that is the case? Thanks!

EDIT: Furthermore, how does https://cloudnative-pg.io/plugin-barman-cloud/docs/retention/ ("The Barman Cloud Plugin supports automated cleanup of obsolete backups via retention policies, configured in the .spec.retentionPolicy field of the ObjectStore resource.") square with https://cloudnative-pg.io/plugin-barman-cloud/docs/object_stores/#s3-lifecycle-policy ("Barman Cloud uploads backup files to S3 but does not modify or delete them afterward. ") ?

Commencez par les pages de documentation liées sur les stockages d’objets MinIO et la rétention. Vérifiez pourquoi le tenant headless service est requis par rapport au ClusterIP service, et mettez en cohérence la formulation de la politique de rétention avec l’affirmation concernant la politique de cycle de vie S3. Le travail est terminé lorsque la documentation explique clairement le service pris en charge et présente un comportement de rétention cohérent.

Rédigé par le modèle d'indexation à partir du texte de l'issue.