update build container to Debian 11.5 + CernVM-FS 2.10.0 + fuse-overlayfs 1.9 + awscli 1.27.8

[boegel]

This seems to fix the weird problem I was running into when installing Qt5-5.15.2-GCCcore-10.3.0.eb when I was using an AWS VM as a build node that is discussed in detail in easybuilders/easybuild-easyconfigs#16614:

/tmp/boegel/easybuild/build/Qt5/5.15.2/GCCcore-10.3.0/qt-everywhere-src-5.15.2/qtbase/bin/qmake -install qinstall /tmp/boegel/easybuild/build/Qt5/5.15.2/GCCcore-10.3.0/qt-everywhere-src-5.15.2/qtbase/include/QtGui/QGenericPlugin /cvmfs/pilot.eessi-hpc.org/versions/2021.12/software/linux/aarch64/graviton3/software/Qt5/5.15.2-GCCcore-10.3.0/include/QtGui/QGenericPlugin
Error copying /tmp/boegel/easybuild/build/Qt5/5.15.2/GCCcore-10.3.0/qt-everywhere-src-5.15.2/qtbase/include/QtGui/QGenericPlugin to /cvmfs/pilot.eessi-hpc.org/versions/2021.12/software/linux/aarch64/graviton3/software/Qt5/5.15.2-GCCcore-10.3.0/include/QtGui/QGenericPlugin: Cannot create /cvmfs/pilot.eessi-hpc.org/versions/2021.12/software/linux/aarch64/graviton3/software/Qt5/5.15.2-GCCcore-10.3.0/include/QtGui/QGenericPlugin for output
make[3]: *** [Makefile:87752: install_gen_headers] Error 3

There were some weird symptoms with the old fuse-overlayfs version (v0.3) that suggest we were hitting a bug, which only seems to manifest on AWS VMs for some reason (probably related to the filesystem type that's being used for the overlay directories).

In addition, it looks like using fuse-overlayfs v1.9 in Debian 11.5 finally fixes the problems we had we recent versions of fuse-overlayfs (cfr. containers/fuse-overlayfs#232) 🥳

Once the build container image is rebuilt, we'll also need to update the build_container.sh script in the https://github.com/EESSI/software-layer/ repo (to use debian11 instead of debian10).

[boegel]

To fix the issue with the tests, I propose we skip the build-macos-package workflow job for now, see #134