[CBM] collect-logs fails if backup metadata is in glacier storage

What is the problem?

A customer found that when running cbbackupmgr collect-logs it failed with:

failed to get repository metadata: failed to get metadata for repository '7d5aba93-815b-4722-ab1e-efee073689d6': failed to get repository info file: failed to fetch repository '.info' file: InvalidObjectState: The operation is not valid for the object's storage class 

After checking in the S3 console we saw that this file was in glacier storage. After fixing this a further run failed with the same error but with backup-meta.json.

What is the solution?

We should ensure that collect-logs works on glacier style storage on AWS, GCP and Azure. Furthermore, if possible, make it best-effort: even if some files cannot be accessed we should not fail (or have an option to not fail) the overall log collection.