Add support for requester pays with credential_chain

DuckDB recently [added support](https://github.com/duckdb/duckdb/pull/18258) for AWS requester pays. However it only seems to work when specifying credentials using config proivider with key_id/secret:

```
CREATE OR REPLACE SECRET secret (
TYPE s3,
KEY_ID '',
SECRET '',
REGION 'us-east-1',
REQUESTER_PAYS true
);
```

But using it with credentials chain gives: `duckdb.duckdb.BinderException: Binder Error: Unknown parameter 'requester_pays' for secret type 's3' with provider 'credential_chain`
```
CREATE OR REPLACE SECRET secret (
TYPE s3,
PROVIDER credential_chain,
CHAIN config,
REQUESTER_PAYS true
);
```

This is inconvenient for using it in AWS services with task role-based credentials, where there's not an easy way to directly get explicit key_id/secret tokens.

Reproduce the two CREATE OR REPLACE SECRET examples and compare the accepted parameters for the config provider with those for credential_chain. Trace the S3 secret parameter handling for REQUESTER_PAYS; done means the credential_chain form accepts the option and works with task-role credentials.

Written by the indexing model from the issue text.