This was becoming increasingly hard to maintain, so I have decided to generate the methods instead.

Every method defined on DuckDBPyConnection now lives in tools/pythonpkg/scripts/connection_methods.json

They look like this:

	{
		"name": "register_filesystem",
		"function": "RegisterFilesystem",
		"docs": "Register a fsspec compliant filesystem",
		"args": [
			{
				"name": "filesystem",
				"type": "str"
			}
		],
		"return": "None"
	}

From this, we generate sections of code inside of:
tools/pythonpkg/duckdb/__init__.py
tools/pythonpkg/duckdb-stubs/__init__.pyi (DuckDBPyConnection)
tools/pythonpkg/duckdb-stubs/__init__.pyi (duckdb)
tools/pythonpkg/src/pyconnection.cpp (InitializeConnectionMethods)

From now on, when adjusting or creating a new connection method, the connection_methods.json file should be updated.

Old Process

• Create a C++ function in pyconnection.hpp and pyconnection.cpp
• Add a pybind definition for it inside pyconnection.cpp
• Create a wrapper C++ function in connection_wrapper.hpp and connection_wrapper.cpp
• Add a pybind definition for it inside duckdb_python.cpp
• Add it to duckdb-stubs/__init__.pyi for both the DuckDBPyConnection method and the corresponding wrapper method.
• Add the wrapper connection method to duckdb/__init__.py (expose the symbol from duckdb.duckdb)

New Process

• Create a C++ function in pyconnection.hpp and pyconnection.cpp
• Update the connection_methods.json
• Run make generate-files

Some issues encountered:

• values didn't take the optional connection as a keyword argument, now it does
• arrow and df are overloaded twice, once for from_arrow/df and another for to_arrow/df.
  We now define these in C++ because it's easier (pybind11 handles the overloading on the Python side).