Draft: Properties for Supercube, instead of setter/getter

@hjanssen Once we discussed the idea to change from setter/getter methods to properties.

I have started with this work at the supercube. By no means is this a decision! This is meant as a starting point, if this is beneficial for the user. And what the best way is to implement the "same" property behavior for different outputs. So far I have implemented two different version.

The first version used for support_input_x_x and suport_output_1-2_1-2 are "real" properties.

The second version (support_output_3_1, t13_1-3 and voltage_measurement_channel_1-4) is using a Descriptor. This way of the implementation looks to me much cleaner and for the user is does not make a difference. The only "downside" is that the developer has to define explicetly the behavior if the parameter is readonly -> raise AttributeError(msg), otherwise it is possible to overwrite the property...