Add new CPU archs in CI Tests workflow

[ppigazzini]

Add CPU archs: armv8-dotprod, riscv64 and ppc64le.
The last two archs are built using QEMU multiarch docker container.

References:
https://docs.docker.com/build/building/multi-platform/
https://github.com/docker/setup-buildx-action
https://github.com/docker/setup-qemu-action
https://github.com/tonistiigi/binfmt
https://stackoverflow.com/questions/72444103/what-does-running-the-multiarch-qemu-user-static-does-before-building-a-containe

closes #4718

No functional change

[snicolet]

Thanks for the PR :-)

It is not exactly related to your patch, but I have a general question concerning the artifact binaries we compile via Github actions: do we use fixed gcc and clang compiler versions, or always ask for the latest gcc/clang versions?

It seems to me that using the latest compiler versions is risky, because compilers could introduce bugs in their updates (it happened to us before, and we sent a crashing SF binary to TCEC because of a bug in the pthread library used by a specific gcc version) and we would not have time to test enough if the compiler changes just before a major SF release.

We could even go as far as deciding that all SF 17 development should be made using the same compiler.

[ppigazzini]

Windows binaries are built with gcc from msys2, which is a rolling distribution. I encountered a loop of dependency for some packages when I tried to downgrade by hand to an earlier version of msys2 gcc. We can switch to a msys2 clang build In case of an issue with the last version of msys2 gcc.
For Linux we are setting gcc 11.

Stockfish/.github/workflows/stockfish_binaries.yml

Lines 88 to 92 in 65ece7d

	- name: Install fixed GCC on Linux
	if: runner.os == 'Linux'
	uses: egor-tensin/setup-gcc@v1
	with:
	version: 11

[snicolet]

Merged via 4c43e1e, thanks :-)

Thanks also for the clarification on the compiler for our binaries. I would think the rolling distribution for Windows build may be a little bit dangerous.