mvd: bugfix in the coordinate transformation
A bugfix in the coordinate transformation of MVD hits.
fSensor->TopToPixel(local, indexX, indexY); is called with the array of size 2 (local[2]), while it assumes the size of 3:
Because of this bug, MVD hits sometimes get bogus values in Z, for example X -0.0901254 Y -0.86012 Z 1.10751e+19
This MR should fix the problem of the hanging CA tracking in the other MR: !1557 (diffs)
In addition, I'll add an extra check of the input data in the CA tracking later.