Duckdb driver should look for credentials in the default provider chain for AWS S3

[GabeInDevOps]

Rather than needing to create, manage and pass an AWS Access and Secret key for the Duckdb driver to read from S3, it should look for credentials in the default provider chain. This is best practice and helps increase the security posture of Cube.

This can be fixed by running the following against duckdb:

CREATE SECRET (
      TYPE S3,
      PROVIDER CREDENTIAL_CHAIN
  );