Feat/S3 provider - set default account id, bucket name and object name; support s3 notification based event trigger

[danxie1999]

Why?

As part of our enterprise deployment, we run three instances of ADF across three separate AWS Organizations: Development Organization, Integration Organization, and Production Organization. Each organization may have different S3 Source Provider Bucket names. To enable the reuse of deployment maps across these organizations, it is necessary to define the default 's3-source-bucket-name' in the respective 'adf-config' file of each organization.
Additionally, the current S3 provider in the deployment map does not support default values for the S3 bucket name, object name, and Account ID. By introducing these default values, it simplifies the definitions of deployment maps and centralizes the management of these properties.
Furthermore, using S3 notification events and EventBridge rules to trigger source pipelines is more efficient than AWS CodePipeline polling. AWS specifically recommends this event-based approach for detecting changes over traditional pipeline polling methods

What?

1. The S3 provider has been updated to include default properties for the S3 bucket name, S3 object, and account ID of the bucket. These properties can now be set centrally and used throughout the application.
2. A new property poll_for_changes had been added to the S3 provider, if set False, S3 notification events and triggers will be enabled instead of polling pipelines.
3. A new function has been added to forward S3 events from other AWS accounts to the current account. This function sets up an event rule in the target account to capture S3 events and forwards them to the current account's event bus, enabling cross-account event processing.

These changes will improve the ADF's ability to manage Multi-Organization S3 bucket configurations, automate data processing pipelines, and integrate with S3 buckets across multiple AWS accounts.

[AndyEfaa]

Thank you. Looks already very good.