fix(s3): objectLockEnabled null error when objectLockDefaultRetention is set to undefined

[nithin-kamal]

Issue #34709

Closes #34709 .

Reason for this change

The root cause is that when Object Lock is disabled (i.e., setting the property ObjectLockDefaultRetention to undefined), the generated CloudFormation template ends up with a null value for ObjectLockEnabled. This leads AWS S3's handler to fail because it attempts to call .booleanValue() on a null, causing a runtime InternalFailure.

Description of changes

If the ObjectLockDefaultRetention is undefined (Object Lock Disabled), the ObjectLockEnabled prop is omitted now. Thereby solving the null value error. No side effects as omitting a prop that is disabled

Describe any new or updated permissions being added

None

Description of how you validated changes

Updated unit tests and snapshots from integration test.

Checklist

• [ x ] My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[aws-cdk-automation]

(This review is outdated)

✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.

[iankhou]

Thanks for your contribution, looks good!

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

This pull request has been removed from the queue for the following reason: checks failed.

The merge conditions cannot be satisfied due to failing checks:

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

[aws-cdk-automation]

This PR has been in the CHANGES REQUESTED state for 3 weeks, and looks abandoned. Note that PRs with failing linting check or builds are not reviewed, please ensure your build is passing

To prevent automatic closure:

• Resume work on the PR
• OR request an exemption by adding a comment containing 'Exemption Request' with justification e.x "Exemption Request: "
• OR request clarification by adding a comment containing 'Clarification Request' with a question e.x "Clarification Request: "

This PR will automatically close in 14 days if no action is taken.

[aws-cdk-automation]

This PR has been deemed to be abandoned, and will be automatically closed. Please create a new PR for these changes if you think this decision has been made in error.

[github-actions]

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.