Destination S3 - connector check ignores the s3_bucket_path

[haithem-souala]

Fix for #15195 & #11871

[CLAassistant]

All committers have signed the CLA.

[marcosmarxm]

@sashaNeshcheret can you review this contribution?

[marcosmarxm]

/test connector=connectors/destination-s3

🕑 connectors/destination-s3 https://github.com/airbytehq/airbyte/actions/runs/2792385510
❌ connectors/destination-s3 https://github.com/airbytehq/airbyte/actions/runs/2792385510
🐛 https://gradle.com/s/usqal4x5btr3c

Build Failed

Test summary info:

Could not find result summary

[haithem-souala]

Hey @sashaNeshcheret, could you review this PR please?

[marcosmarxm]

/test connector=connectors/destination-s3

🕑 connectors/destination-s3 https://github.com/airbytehq/airbyte/actions/runs/2843210270
✅ connectors/destination-s3 https://github.com/airbytehq/airbyte/actions/runs/2843210270
No Python unittests run

Build Passed

Test summary info:

All Passed

[marcosmarxm]

@sashaNeshcheret can you do the final approval here?

[sashaNeshcheret]

Hi @haithem-souala, sorry i've not a chance to make review earlier.
I've tested PR and it really covers case when user has just read permissions on s3 and in such case we are trying to create new object(with bucket name) instead of using path that specified in config. From my perspective it can be properly published and merged. Thanks for your work.
CC: @marcosmarxm

[marcosmarxm]

/publish connector=connectors/destination-s3

🕑 Publishing the following connectors:
connectors/destination-s3
https://github.com/airbytehq/airbyte/actions/runs/2917700974

Connector	Did it publish?	Were definitions generated?
connectors/destination-s3	✅	✅

if you have connectors that successfully published but failed definition generation, follow step 4 here ▶️