[AWS::S3::Bucket] Enabling ObjectLock on an existing bucket is now supported

### Name of the resource

AWS::S3::Bucket

### Resource name

_No response_

### Description

According to https://aws.amazon.com/about-aws/whats-new/2023/11/amazon-s3-enabling-object-lock-buckets/ , you can now enable Object Lock on an existing bucket.

However, the CloudFormation change set indicates that it requires replacement:

```json
[
{
"type": "Resource",
"resourceChange": {
"action": "Modify",
"logicalResourceId": "Bucket83908E77",
"physicalResourceId": "foostack-bucket83908e77-x5oftmkjofzs",
"resourceType": "AWS::S3::Bucket",
"replacement": "True",
"scope": [
"Properties"
],
"details": [
{
"target": {
"attribute": "Properties",
"name": "ObjectLockEnabled",
"requiresRecreation": "Always"
},
"evaluation": "Static",
"changeSource": "DirectModification"
}
]
}
}
]
```

### Other Details

Originally discovered via: https://github.com/aws/aws-cdk/issues/29168

Review the AWS::S3::Bucket resource behavior described in the issue and compare it with the linked AWS announcement and CloudFormation change-set output. Determine where the resource specification represents ObjectLockEnabled and verify that enabling it on an existing bucket no longer requires replacement; the payload names no repository files or tests.

Written by the indexing model from the issue text.