Use vcpkg overlay ports from extension-ci-tools instead of the registry repo

[samansmink]

Recently we added a vcpkg registry which is now hardcoded across extensions, see duckdb/extension-template#119.

This makes maintaining extensions more complicated and I think that should be moved out of the individual extension repositories and into the central location where we can easily maintain this.

The best candidate for this seems to me to use the overlay ports in this repo that were added #164 instead of adding the registry to every extension.

Solution would be to:

• add default-enabled option to extension-ci-tools makefiles to pass the path to the overlay ports
• remove registry reference from extension-template and bump extension-ci-tools to use the overlay ports from there instead

@carlopi

[carlopi]

I am not sure I get what's the goal of the infrastructure in the first point, would it not be viable to have extension-template vcpkg.json be:

{
        "dependencies": [
                "openssl"
        ],
        "vcpkg-configuration": {
                "overlay-ports": [
                        "./extension-ci-tools/vcpkg_ports"
                ]
        }
}

Are ever reason to NOT have it point to extension-ci-tools?

[carlopi]

I think we are good here with duckdb/extension-template#120

[carlopi]

Actually, it needs to be done elsewhere, reopening for tracking, but we have a path, cool