setting SECRETS SCOPE by ENDPOINT?

duckdb documentation describes how to create [multiple secrets for the same service](https://duckdb.org/docs/configuration/secrets_manager), e.g. if we have two S3 buckets that need different credentials. The directions indicating scoping based on _bucket name_.

However, I commonly encounter the case where I need to access two different S3 services at different _endpoints_ -- for instance, S3 buckets data.source.coop , S3 buckets on a local minio instance, S3 buckets on AWS. It would be natural to scope these by the _endpoint name_, not the bucket name -- I may have the same credentials for multiple buckets, and I may have the same bucket name on different endpoints.

I think it is something of a bug that scope focuses on bucket name but ignores endpoint. Would you consider adding support for this?