Propagate TrackingGeometry conditions data to TrackingGeometrySvc and detector store.

For athenaMT the TrackingGeomtry will become conditions data. All clients need to be migrated to use the conditions data instead of the TrackingGeometrySvc. In the transition phase there will be clients which use the service, and there will be clients which use the conditions data.

In some places TrackingVolume identity comparisons are performed by comparing pointers. This fails in case the volumes originate from different instances of otherwise identical TrackingGeoemtries. Thus, in the transition phase in which the TrackingGeometry is obtained by both, the conditions data and the service, such comparisons will fail and lead to different results. To mitigate this problem, the TrackingGeometry conditions algorithm will now optionally propagate the conditions data to the TrackingGeometrySvc and the detector store.

Currently the TrackingGeometry conditions algorithm is not in use in production code, so this commit will not have any effect. It is meant to allow an incremental migration of the clients from using the service to conditions data.