Tracking4D: Use local coordinates for cluster association

Tracking4D currently uses global coordinates to calculate the distance between cluster and track but the spatial cuts are assumed in local coordinates (spatial_cut_rel reuses the detector resolution which is local). This leads to wrong cuts if one of the telescope planes is rotated around the z-axis. The association should be done in local coordinates only, which is also how it is done in the DUTAssociation module.