add object lock/retention to BSL log/annotation

[kaovilai]

Describe the problem/challenge you have

Using api like https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObjectLockConfiguration.html (supported by minio)
[### Required permissions
Object Lock operations require specific permissions. Depending on the exact operation that you're attempting, you might need any of the following permissions:

• s3:GetBucketObjectLockConfiguration
• s3:GetObjectRetention](https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lock.html#object-lock-best-practices:~:text=project%20is%20complete.-,Required%20permissions,s3%3APutObjectRetention,-For%20a%20complete)

Describe the solution you'd like

Update our docs to include perm if needed, and during validation of BSL, add lock/retention settings to BSL annotations.

Anything else you would like to add:

This will help us in one of following

1. Tell user early that this bucket may not work per current limitations resolving in Avoid overwriting during backup to support object lock enabled buckets #8686
2. Use as basis for different velero-backup.json PutObject behavior to solve in Avoid overwriting during backup to support object lock enabled buckets #8686

Environment:

• Velero version (use velero version):
• Kubernetes version (use kubectl version):
• Kubernetes installer & version:
• Cloud provider or hardware configuration:
• OS (e.g. from /etc/os-release):

Vote on this issue!

This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.

• 👍 for "The project would be better with this feature added"
• 👎 for "This feature will not enhance the project in a meaningful way"