(s3): addEventNotifications custom resource does not allow logical ID renaming

### Describe the bug

When the custom resource handler for a bucket's object notifications is renamed, the bucket is left without notifications at all.

### Expected Behavior

Not that.

### Current Behavior

The bucket doesn't have notification handlers at all.

### Reproduction Steps

- Deploy a stack with a Bucket with Object Notifications enabled
- Rename the ID for the object notifications and redeploy
The bug is here:

https://github.com/aws/aws-cdk/blob/d644c00bc8876d15608b11bad13f62f3e3837dc2/packages/%40aws-cdk/aws-s3/lib/notifications-resource/lambda/index.py#L28

The sequence of events is as follows:

- (Create new custom resource) Put NEW object notification configuration
- (Delete old custom resource) Put EMPTY object notification configuration

End result: no notification config at all

### Possible Solution

When we fix this, don't forget to update the "important cases to handle" section in the `custom-resources` README.

### Additional Information/Context

_No response_

### CDK CLI Version

-

### Framework Version

-

### Node.js Version

-

### OS

-

### Language

Typescript, Python, .NET, Java, Go

### Language Version

_No response_

### Other information

_No response_

Start with packages/@aws-cdk/aws-s3/lib/notifications-resource/lambda/index.py at the linked handler location and trace the create and delete operations for renamed custom resources. Then read the “important cases to handle” section in the custom-resources README. Done means redeploying after a logical ID rename preserves the bucket’s object notification configuration and the README reflects the handled case.

Written by the indexing model from the issue text.