Use the full names when registering multiparameters

[jenshnielsen]

For some reason multiparameters were unlike all other paramters not using the full name. This is both confusing and problematic if you have two multiparameters with the same short name (e.g. from different channels)

@astafan8 Any suggestions for other ways of doing it?

Note This is a breaking change but I don't see any way around it.

[codecov]

Codecov Report

Merging #2317 into master will decrease coverage by 0.00%.
The diff coverage is 83.33%.

@@            Coverage Diff             @@
##           master    #2317      +/-   ##
==========================================
- Coverage   61.87%   61.86%   -0.01%     
==========================================
  Files         201      201              
  Lines       26122    26119       -3     
==========================================
- Hits        16162    16159       -3     
  Misses       9960     9960              

[astafan8]

@astafan8 Any suggestions for other ways of doing it?

no, becasue it think this IS the correct way of doing it.

Note This is a breaking change but I don't see any way around it.

me neither. i'd say this is a discovery of a bug, which is great.

---

Another way of fixing this PR could be to change __str__ to just return self.full_name as opposed to the current implementation here https://github.com/QCoDeS/Qcodes/blob/master/qcodes/instrument/parameter.py#L387 . I actually think that changing __str__ must also be done regardless of this PR :)

[jenshnielsen]

The changes to not use str(parameter) are actually only for consistency. The real issue is the fix
from self._register_parameter(multiparameter.names[i], to self._register_parameter(multiparameter.full_names[i],

[astafan8]

The changes to not use str(parameter) are actually only for consistency

that's fine, it's just that when reviewing i had to look and see what str(parameter) does to confirm the consistency ;)