Merge branch 'staging'

This adds Ubuntu Jammy to the CI pipeline.
This required significant efforts. It seems like when Ubuntu "tighten security", they do in in a manner that breaks CI work-flows (including for a long time, just upgrading the distribution inside their official container image).
I was unable to get the Jammy build/test container worning without running the build as root! That's really, really bad!

Author: jgaa

README.md

@@ -256,15 +256,16 @@ These are the operating systems where my Continues Integration (Jenkins) servers
 
  - Debian Testing
  - Debian Bookworm
- - Debian Bullseye (Stable)
+ - Debian Bullseye
  - Debian Buster
  - Windows 10 / Microsoft Visual Studio 2019, Community version using vcpkg for dependencies
  - Ubuntu Xenial (LTS)
+ - Ubuntu Jammy (LTS)
 
 Support for MacOS has been removed after Apples announcement that their love for privacy was just 
 a marketing gimmick.
 
-Fedora is currently disabled in my CI because of failures to start their Docker containers. (Work in progress). Ubuntu Jammy don't work in docker with my Jenkins  CI pipeline, so I have no reliable way to test it. Windows 11 cannot be run on my KVM /QEMU system, because it don't support "secure" boot, so I have no way to test it.
+Fedora is currently disabled in my CI because of failures to start their Docker containers. (Work in progress). 
 
 The Jenkins setup is [here](ci/jenkins).
 

ci/jenkins/Dockefile.ubuntu-jammy

@@ -14,7 +14,8 @@ RUN DEBIAN_FRONTEND="noninteractive" apt-get -q update &&\
 # Set user jenkins to the image
 RUN useradd -m -d /home/jenkins -s /bin/sh jenkins &&\
     echo "jenkins:jenkins" | chpasswd &&\
-    mkdir -p /home/jenkins/build/workspace/restc-staging
+    mkdir -p /home/jenkins/build/workspace/restc-staging &&\
+    mkdir -p /run/sshd
 
 # Standard SSH port
 EXPOSE 22