fix: Build libzmq locally to work on all host types

[pabera]

This PR addresses and aims to resolve the building issues associated with libzmq across all platforms.

Previously, the strategy of utilizing pre-built libzmq binaries within Docker environments was intended to streamline development processes. However, this approach did not achieve the desired outcome of creating a seamless and frustration-free development experience.

We are shifting back to locally building libzmq. This process is now consolidated within a dedicated Dockerfile, ensuring that the build is required only once. Once the build is completed, it becomes readily accessible and shareable across all Docker environments, significantly improving the development workflow.

Introduces changes

• Outsourced libzmq build into local Docker build. Artefacts are shared between Dockerfiles
• Changed naming convention for Docker files: [name].Dockerfile to Dockerfile.[name] (easier to find in file tree)
• Updated documentation. Made it easier to copy/paste individual commands by separating them

Should solve:

• installation: untar libzmq in venv folder instead of /usr/local #2305 (thanks @notapirate, I took a bit of inspiration for my solution from your work)
• Fix Docker for pyzmq #2167

Relates to:

• docker: update jukebox/mpd base image to debian:bookworm #2299 (We should not update to Bookworm yet for Docker just to resolve libzmq issues)

Test

• Mac
• Windows (with WSL)
• Linux

[pabera]

I have only tested this on Mac so far. If others could help trying this out on their machine, that would be great.

[pabera]

Tested this on Windows (WSL, x86_64) successfully.

[s-martin]

@notapirate could you add a comment, with which platform/configuration it works for you?

[notapirate]

Sure, I tested this on Linux (Arch Linux, x86_64) successfully.

[s-martin]

On Windows 11 building the images works now, also running :)

[notapirate]

@pabera you may want to double-check changes in docker.md, I think the item numbering got messed up :)

[s-martin]

@pabera i just merged #2310, if you use the new future3/develop you could remove the markdownlint-disable / restore tags from docker.md, because this is now configured globally.

[s-martin]

@pabera you may want to double-check changes in docker.md, I think the item numbering got messed up :)

Not necessary, „markdown magic“ renders the numbering correctly.

[s-martin]

@pabera
in line 379 and 393 are two more <!-- markdownlint tags, could you remove them as well?

[s-martin]

After #2312 is merged the error in the CodeQL action should be gone.