adding volume and surface ID to trajectory

**Is your feature request related to a problem? Please describe.**
The acts multitrajectoryhelper provided volume and surface id for each hit. We already have chi2 for each hits in the trajectory data structure (see https://github.com/eic/EDM4eic/blob/ed58344685dd40c0e35154ef0ae7eca3f709aa47/edm4eic.yaml#L330)
. Adding those geometry info helps the tracking performance analysis.

I propose to add the following four integer vectors:
( see https://github.com/acts-project/acts/blob/main/Core/include/Acts/EventData/MultiTrajectoryHelpers.hpp)
measurementVolume, measurementLayer, outlierVolume, outlierLayer

Start with the trajectory definition referenced in edm4eic.yaml around line 330, then compare the proposed fields with Acts' Core/include/Acts/EventData/MultiTrajectoryHelpers.hpp. Trace how the data model is generated and verify that measurementVolume, measurementLayer, outlierVolume, and outlierLayer are available for trajectory hits; done means the geometry information supports tracking-performance analysis.

Written by the indexing model from the issue text.