Describe the bug
The addition of using the logStreamName as the PhysicalResourceId breaks the lifecycle of the custom resource. Since the logStreamName is different for every execution the custom resource treats updates as a delete so every update will do a delete. Then the delete fails because it will return a different PhysicalResourceId than it received which will cause an error.

Expected behaviour
The life cycle of the custom resource should be handled correctly and the PhysicalResourceId should be deterministic through out the whole life cycle.

Environment (please complete the following information):

• Node.js: 22
• Middy: 7.1.7
• AWS SDK N/A