[AWS::Lambda::EventSourceMapping] - [Enhancement] - Drift Detection Support

### Name of the resource

AWS::Lambda::EventSourceMapping

### Resource name

_No response_

### Description

Drift detection is not supported for [AWS::Lambda::EventSourceMapping](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-lambda-eventsourcemapping.html).

### Other Details

Here's maybe a scenario to explain why this would be needed:

If I create an SQS EventSourceMapping for a Lambda, and then later delete and recreate that queue, the EventSourceMapping will go from ENABLED state to DISABLED state (AWS Lambda does this) and it does not switch back. Cloudformation does not detect this drift and consequently, lambda functions fail to get invoked thus breaking apps.

Ref:
- https://stackoverflow.com/questions/52923002/aws-sqs-lambda-trigger-disabled-automatically

Start by reading the AWS::Lambda::EventSourceMapping documentation linked in the issue and the CloudFormation drift detection documentation. Investigate how the roadmap repository tracks coverage for this resource; done means drift detection identifies the mapping changing from ENABLED to DISABLED after its SQS queue is recreated.

Written by the indexing model from the issue text.