workaround for RD53a quad modules to do a complete meta_tuning

Meta_tune_threshold.py does not work for rd53a quad modules due to the stuck pixel scan. If one sets the start_column=128everything works fine. Since in the scan_stuck_pixel stuck pixels in the the SYNC FE can not be identified, and are ignored it does make a difference to set the start_column=128. The chip_type is queried in the noise occupancy scan. Maybe someone has a better idea how to get the chip_type. Related to #416 (closed)