Add the possibility to set edm4hep::utils::ParticleIDMeta via the IMetadataSvc

[tmadlener]

BEGINRELEASENOTES

• Make it possible to use edm4hep::utils::ParticleIDMeta with the MetadataSvc
  • Add template specializations for get and put that defer to the corresponding utility calls in EDM4hep
  • Add tests to ensure that metadata is indeed usable this way with the utilities in EDM4hep

ENDRELEASENOTES

This would be option 1 sketched out in #272

• Small test that checks that metadata is also usable outside of framework
• Needs Add documentation and a convenience overload to the ParticleID utilities EDM4hep#395

[tmadlener]

I have added a "small" test case that runs similar checks as in the functional algorithm as a standalone application (effectively hard-coding the expected parameter and algorithm names). I have done it in c++ because the PIDHandler is not yet really usable in python (see key4hep/EDM4hep#396).

Once the nightly builds have picked up key4hep/EDM4hep#395, CI should also start to pass again (tomorrow).

[tmadlener]

Since I touched the ExampleFunctionalProducerMultiple to also create ReconstructedParticles, I had to fix a few other tests to also make them pass. The alternative would be to introduce a dedicated producer for the ParticleID metadata tests. I am not sure if it's worth it, but it can obviously be done.

[jmcarcell]

I'll give this another look and update key4hep/k4MarlinWrapper#216 to use this to see if anything is missing between today and tomorrow.

[jmcarcell]

All good related to key4hep/k4MarlinWrapper#216

[jmcarcell]

Merge?

As a note once we stop using Ubuntu 22.04 (because there are already builds for Ubuntu 24.04, key4hep/key4hep-spack#700) we can use <format>; anyway Gaudi doesn't support GCC 11 anymore...

[tmadlener]

Merge?

Yes, this is done from my point of view, unless someone still has comments.