Make calculate registration more robust in table column handling on reruns

[jluethi]

Calculate registration adds 3 new columns to existing ROI tables. translation_z, translation_y, translation_x

When they already exist, it's not correctly handled. The expectation would be that those columns are overwritten. Instead, they are combined with appendices, leading to the new columns being:

x_micrometer
y_micrometer
z_micrometer
len_x_micrometer
len_y_micrometer
len_z_micrometer
translation_z_x
translation_y_x
translation_x_x
translation_z_y
translation_y_y
translation_x_y

This makes downstream tasks fail.

=> Handle existing columns better in the calculate registration task