Test dockerized compilation in Alpine:latest and Ubuntu:20.04

[carlopi]

Adding CI workflow for testing DuckDB compilation in dockerized environments.

Script currently provided for Alpine:latest and Ubunutu:20.04.
Those double down also as blueprints for how to compile and build DuckDB main binaries in those architectures / what dependencies are needed.

More tests are very welcome, it's a matter of adding a line per distribution to scripts/test_docker_images.sh.

Adding a partial revert of #11663 where I propose a different fix to #11640 via providing a define, unsure whether this will be sufficient. Asking @zmbc if he could either provide a docker script showing the problem, I haven't managed to reproduce, and/or testing in its configuration with this alternative solution.

In the current form fixes #11703, otherwise merging only the first commit this should at the very least provide a reproduction and means to avoid similar regressions.

[carlopi]

Push for these tests is by @szarnyasg, adding in as reviewer.

[carlopi]

Also pinging @Flogex, since a PR of theirs (#11635) introduced the CMAKE_CURRENT_FUNCTION_LIST_DIR that is malfunctioning in the docker setup.

I have yet to check on their setup, at Flogex/duckdb-extension-template@7aa87de, to double check whether this change might work for everyone.

[Flogex]

@carlopi Looks like CMAKE_CURRENT_FUNCTION_LIST_DIR is new in CMake 3.17, the minimum required version for DuckDB is 3.5. I didn't check this, sorry.

Using DUCKDB_MODULE_BASE_DIR as introduced in this PR works in a setup that includes the DuckDB CMake project as subdirectory and is the nicer approach IMO. 👍

[Mytherin]

Thanks!

[zmbc]

Unfortunately, this fix doesn't work in a conda environment, in the same way as described in #11640. It is enough to call fallocate but does not include the flags. I am a bit out of my depth as to why it seems that in many setups, the falloc headers are included automatically, apparently including Alpine, although a linux-headers package is available for Alpine. Any pointers?

[carlopi]

Unfortunately, this fix doesn't work in a conda environment, in the same way as described in #11640. It is enough to call fallocate but does not include the flags. I am a bit out of my depth as to why it seems that in many setups, the falloc headers are included automatically, apparently including Alpine, although a linux-headers package is available for Alpine. Any pointers?

I am happy to dig deeper, would it be possible for you to share instructions on how to reproduce your setup? Basically something in the form like:

docker run -i --rm -v $(pwd):/duckdb --workdir /duckdb ubuntu:20.04 <<< "apt-get update && export DEBIAN_FRONTEND=noninteractive && apt-get install g++ git make cmake ninja-build -y && GEN=ninja make && make clean" 2>&1

where instead you provide how to install conda + how to fetch dependencies + what exact packages are needed ?
I am happy to dig further, but I think you are in a better place to provide description of the exact steps you are following / your setup.

Once I can reproduce, it should be easy(er) to find a way out plus have a way to test no regression will happen for relevant setups.