Follow-up from #15936 - avoid
constantly querying the default-allocator and use the one set in the
`ClientContext` instead.

For now the previous constructor (not requiring an allocator) is kept -
pending removal in the future (this requires changing a few extensions).

Short term goal is being able to build (and test) all relevant Python wheels on a random
commit.
End goal is cleaning up logic from within the YAML files (is main? is tagged with a v?)
to some external yet-to-be-implemented but available manually control workflow.

…le workflow

This makes so all extensions go through the same path.
signing_pk option of the build_all_extensions workflow is left in place as caution measure, but can/should be removed

See https://en.cppreference.com/w/cpp/thread/thread/hardware_concurrency

Short term goal is being able to build (and test) all relevant Python
wheels on a random commit.

End goal is cleaning up logic from within the YAML files (is main? is
tagged with a v?) to some external yet-to-be-implemented but available
manually control workflow.

This makes so all extensions go through the same path. signing_pk option
of the build_all_extensions workflow is left in place as caution
measure, but can/should be removed

Some more touches to Pyodide tests / CI, plus adding @cpcloud's
#15862 that enabled Pyodide 0.27.2.

…16000)

See https://en.cppreference.com/w/cpp/thread/thread/hardware_concurrency

Should fix
#14903 (comment)

Since these functions now rely on ICU for their functionality - just
moving them to ICU simplifies things and enables auto-loading for
clients that do not have ICU installed by default (e.g. WASM).

…access is disabled

Build and test the 2025a time zone data

fixes: duckdblabs/duckdb-internal#4119

…_extensions` is set to false (#16014)

…s disabled (#16015)

This partially reverts the changes made in
#14568

We used to fully disallow `ATTACH` when this setting was disabled. We
now allow attaching, and fail later based on the
`allowed_directories`/`allowed_paths `. This allows us to still attach
files if they are within the allowed set of paths.

Storage extensions do not necessarily abide by these rules, however. For
now we just move back to disallowing `ATTACH` of non-DuckDB files
entirely if the setting is set to false.

Build and test the 2025a time zone data

fixes: duckdblabs/duckdb-internal#4119

#16017 @cpcloud

Fix duckdblabs/duckdb-internal#3785.
Fix duckdblabs/duckdb-internal#4092.

Addresses duckdblabs/duckdb-internal#4110

Sampling has bad memory management right now, which is causing larger
ingestions to fail. In the interest of releasing early next week, it's
probably best that it is removed and later added when memory issues are
resolved