Some nice-to-have features

[Sam Ansmink]

This issue groups a few nice-to-have features we would like to see added. Issue will be updated as we think of more, feel free to contribute ideas

• Update notifier: Third party extension maintainers should notified through some way of a new DuckDB release.
• Some standardized way of getting documentation on an extension (either a block of text or a url to the docs)
• Auto-Install extension dependencies
• Use duckdb clang-format, clang-tidy, and editorconfig
• Ensure release also produce binaries as artifacts on github for all builds
• Change extension script path: It currently prefixes all paths with the extension namespace, this should be a configurable path to allow deploying multiple extensions to the same directory allowing a single set custom_extension_repository to easily access a bunch of extensions that are separately managed
• CI to ensure both linkage of the static extension and loadable extension are correct: especially when an extension links against other libraries, errors here are easy to make rendering the extension unloadable.
• Explain how the build process works of extensions: clarify that duckdbs cmake file is the root cmakefile
• Document and/or provide template for linking dependencies to both static lib and loadable extension