S3 lifecycle policy and history files

This is more like a general question about S3 lifecycle policies, since there is some conflicting information about this topic. The docs (https://cloudnative-pg.io/plugin-barman-cloud/docs/object_stores/#s3-lifecycle-policy) explicitly recommend setting an S3 lifecycle policy on the current versions of the objects as well. However, this would also expire history files, which are not touched in the objectstore after transfering them once. Are these archived history files not needed for restoration? Then why archive them? If they are needed, then is there some mechanism that guarantees a timeline switch in each retention window?

Start with the S3 lifecycle policy section linked in the issue and trace how archived history files are used during restoration. Confirm whether the documented lifecycle recommendation can expire them safely and whether a timeline switch is guaranteed within each retention window. Done means resolving the questions and updating the documentation with an unambiguous explanation.

Written by the indexing model from the issue text.