Some metadata about minimum supported version

Adding support for extension authors to add minimum supported DuckDB version for the extension would be nice. Even better, if this could be automatically generated that'd be great.

When trying to add support for the new [gsheet extension](https://duckdb.org/community_extensions/extensions/gsheets.html) for customers we were running into this error:

```
HTTP Error: Failed to download extension "gsheets" at URL "http://community-extensions.duckdb.org/v1.1.1//gsheets.duckdb_extension.gz" (HTTP 403)

Candidate extensions: "postgres", "inet", "https", "delta", "s3"
```

We had `duckdb` (and Rust bindings) pinned at v1.1.1[^1] and were running into this issue with `INSTALL gsheets FROM community;`.

It would be nice if there was a notice somewhere for an extension that would let users know what minimum version of DuckDB they need. Maybe this metadata could also inform a more helpful HTTP error message indicating that you need to upgrade.

To be fair, the Github repo for the repository did mention that v1.1.3 is supported but it didn't say *only* v1.1.3 is supported. Also it would be hard to pull from that for CI unlike a dedicated field in a YAML file.

[^1]: Rust bindings with bundled libducksys are behind and do not have versions v1.1.2 or v1.1.3 yet

No files or tests are named. Start by tracing the community extension install path used by `INSTALL gsheets FROM community;` and the versioned download URL shown in the report. Define the metadata source and whether the finished work must expose the minimum version to users, improve the HTTP error, or both.

Written by the indexing model from the issue text.