iLCSoft v02-03-04 release on EL/Alma9

[tmadlener]

BEGINRELEASENOTES

• Create a first release on EL9 / Alma9
  • Using gcc13, python3.11.9
  • Switching to c++20
• Add Dockerfile to build CVMFS installation container
• Fix a few minor build issues in some packages
• Make all Marlin packages install their artifacts into <prefix>/install instead of only <prefix> to better separate the source code and the installed binaries
• Update packages to the following tags
  • LCIO v02-22-05
  • Marlin v01-19-05
  • MarlinReco v01-36-02
  • MarlinUtil v01-18-02
  • k4geo (lcgeo) v00-21
  • DDMarlinPandora v00-13
  • MarlinTrkProcessors v02-12-07
  • iLCUtil v01-07-03
  • GEAR v01-09-05
  • CEDViewer v01-20
  • CED v01-10
  • KiTrack v01-10-01
  • LCFIPlus v00-11
  • PandoraPFANew v04-15-00

ENDRELEASENOTES

• package versions to release notes
• squash a few commits for a cleaner history to make rebase and merge make more sense
• Test build

[tmadlener]

I have switched to picking up Qt5 and xrootd from the underlying LCG_106 stack, because I could not get a successful build for Qt5 and roots builtin_xrootd didn't work for me either.

I managed to get release-base to build without any manual intervention this way, but for release-ilcsoft there are still a few manual edits necessary to get it to build. As far as I can see the following PRs need to get merged first in order to fully build the stack without manual intervention:

• Move assignments outside of if statement PandoraPFA/PandoraSDK#18 (this one can be avoided by building Pandora with c++17 instead of c++20)
• Fix the dictionary generation on several platforms lcfiplus/LCFIPlus#72

Some other PRs would be nice to have, but are, I think, not critical

• Use recommended way to set the c++ standard via cmake PandoraPFA/PandoraMonitoring#11
• Use the recommended way to set the c++ standard via cmake PandoraPFA/LCContent#23

[tmadlener]

I have moved LCFIPlus into a separate package, because it needs some more dedicated setup for the runtime environment, e.g. ROOT_INCLUDE_PATH has to be populated to avoid runtime issues.