destination-s3: update configs with common defaults

[evantahler]

Some UX updates for destination-s3:

• while still not required, access_key_id and secret_access_key should be shown on the form by default - they are very common (Closes Add always_show: true to S3 Key ID and S3 Access Key #33254)
• Make the default file format CSV

Now, as a note, these changes won't make it airbyte cloud because we have an old version of the connector pinned on Airbyte Cloud (reason: (incorrect filename format, do not use) Adopt java CDK version 0.4.). We'll investigate this when we revisit S3's certification next year. re: #32228 and UUID file names vs numbers.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
airbyte-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 8, 2023 7:22pm

[github-actions]

Before Merging a Connector Pull Request

Wow! What a great pull request you have here! 🎉

To merge this PR, ensure the following has been done/considered for each connector added or updated:

• PR name follows PR naming conventions
• Breaking changes are considered. If a Breaking Change is being introduced, ensure an Airbyte engineer has created a Breaking Change Plan.
• Connector version has been incremented in the Dockerfile and metadata.yaml according to our Semantic Versioning for Connectors guidelines
• You've updated the connector's metadata.yaml file any other relevant changes, including a breakingChanges entry for major version bumps. See metadata.yaml docs
• Secrets in the connector's spec are annotated with airbyte_secret
• All documentation files are up to date. (README.md, bootstrap.md, docs.md, etc...)
• Changelog updated in docs/integrations/<source or destination>/<name>.md with an entry for the new version. See changelog example
• Migration guide updated in docs/integrations/<source or destination>/<name>-migrations.md with an entry for the new version, if the version is a breaking change. See migration guide example
• If set, you've ensured the icon is present in the platform-internal repo. (Docs)

If the checklist is complete, but the CI check is failing,

1. Check for hidden checklists in your PR description

2. Toggle the github label checklist-action-run on/off to re-run the checklist CI.

[gisripa]

s/resist/revisit 😄

[gisripa]

One thing to probably note is, this was intentionally not marked as required because for OSS users deployed on aws instances, they get that from instance profile or other mechanisms

[edgao]

these changes won't make it airbyte cloud

they won't make it to oss either - we're pinning 0.5.1 everywhere