Make CI builds (especially skupper-router image) more production-like

[jiridanek]

This is a follow up to (my) comments on #44. This ticket suggests to consider doing (and eventually do) one or more of the following

• base the skupper-router image on CentOS Stream 8 or UBI 8 Base the Docker image on ubi8 image instead of fedora #84
• build the router with production-like flags, such as the various flavors of -fstack-protector and with -D_FORTIFY_SOURCE=2
  • Build the router container with production-like flags, such as the various flavors of -fstack-protector and with -D_FORTIFY_SOURCE=2 #444
• use RPM .spec file to build the router in the builder image and then install it from that RPM in the deployed image
  • Add rpm .spec to skupper-router project #186
  • WON'T DO, the production image is not using rpm either
• build qpid-proton as a static library and link it into dispatch; possibly use -DCMAKE_INTERPROCEDURAL_OPTIMIZATION=ON and -fno-semantic-interposition (https://fedoraproject.org/wiki/Changes/PythonNoSemanticInterpositionSpeedup)
  • Issue #60: Build skupper-router image using LTO and with static proton libs #96
• use catchsegv or -lSegFault in production build to always dump stacktrace on crash (use addr2line to later decrypt the trace)
• LIBC_FATAL_STDERR_=1
• why our libwebsockets is built with LWS_WITH_LIBUV=ON and LWS_WITH_HTTP2=OFF?
  • fixed by @ajssmith in add lws to image build #369
• set -Eeuo pipefail
• QDROUTERD_AUTO_MESH_DISCOVERY as core skupper-router feature, instead of hacky config file editing during image startup
• some tests for the container image, to be reasonably sure Skupper was not broken by changes
  • Run Skupper integration tests with the skupper-router image #169
  • Issue #371 - Add h2spec container test (inspired by qdr-image tests from @fgiorgetti) #381

[jiridanek]

ad catchsegv: debug: Remove catchsegv and libSegfault (BZ #14913)

[ganeshmurthy]

Most tasks completed