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. ") ?

Inizia con le pagine della documentazione collegate sugli object store MinIO e sulla conservazione. Verifica perché sia richiesto il tenant headless service rispetto al ClusterIP service e concilia la formulazione della policy di conservazione con l'affermazione sulla policy del ciclo di vita S3. Il lavoro è completato quando la documentazione spiega chiaramente il service supportato e presenta un comportamento di conservazione coerente.

Scritto dal modello di indicizzazione a partire dal testo della issue.