[Feat]: Event based detection method for pipeline with S3 data source

### Describe the feature

Pipelines with S3 as data source are using the polling method which will be deprecated https://docs.aws.amazon.com/codepipeline/latest/userguide/trigger-S3-migration-cwe.html

### Use Case

To avoid the deactivation of this pipeline we should move to a event based trigger approach
Here the notification from support

Subject: [Action may be required] AWS CodePipeline is disabling polling in inactive pipelines
CAUTION: This email originated from an external source. Use caution when replying, clicking links, or opening attachments.
Hello,
You are receiving this message because you have one or more polling pipelines in your account. A polling pipeline is defined as a pipeline that has at least one source action configured to poll for changes. The AWS CodePipeline team will be disabling polling in inactive pipelines effective May 25, 2023. An inactive pipeline is defined as one that has not had a pipeline execution started in the last 30 days. Inactive pipelines that only use Amazon EventBridge rule, or AWS CodeStar Connections, or webhooks to trigger the pipeline will not be affected. Additionally, any active pipeline will also not be affected.
We recommend that you update to use Amazon EventBridge, or AWS CodeStar Connections, or webhooks as the trigger mechanism for your source. Follow the instructions in the documentation[1] for making this change. Changing your pipeline from polling to event based will improve performance for pipeline executions by ensuring they respond to source changes quicker.
If you have questions about this change, the AWS Support Team is available on re:Post [2] and via Premium Support [3].
[1] https://docs.aws.amazon.com/codepipeline/latest/userguide/update-change-detection.html
[2] https://repost.aws/tags/TAD_CcYa8ASIKYqZ_uXiwwgA/aws-codepipeline
[3] https://support.console.aws.amazon.com/support
Sincerely,
Amazon Web Services
Amazon Web Services, Inc. is a subsidiary of [Amazon.com](http://amazon.com/), Inc. [Amazon.com](http://amazon.com/) is a registered trademark of [Amazon.com](http://amazon.com/), Inc. This message was produced and distributed by Amazon Web Services Inc., 410 Terry Ave. North, Seattle, WA 98109-5210
docs.aws.amazon.comdocs.aws.amazon.com
[Migrate polling pipelines to use event-based change detection - AWS CodePipeline](https://docs.aws.amazon.com/codepipeline/latest/userguide/update-change-detection.html)
Describes how to update a pipeline for event-based change detection by source type.
Amazon Web Services, Inc.Amazon Web Services, Inc.
[Find Answers to AWS Questions about AWS CodePipeline](https://repost.aws/tags/TAD_CcYa8ASIKYqZ_uXiwwgA/aws-codepipeline)
Browse through AWS CodePipeline questions or showcase your expertise by answering unanswered questions.

### Proposed Solution

Move the pipeline trigger method to an event based trigger approach

### Acknowledgements

- [ ] I may be able to implement this feature request

Start by reviewing the linked AWS documentation on migrating polling pipelines to event-based change detection, then locate how this repository configures pipelines with S3 sources. The issue names no repository files or tests; done means S3-backed pipelines use event-based triggers instead of polling and remain deployable.

Written by the indexing model from the issue text.