Typing of functions with Quantity arguments

[GlaserN]

Describe the bug
Typing of most objects requiring Quantity objects is wrong, requiring mostly float by itself. In order to get the right typing behavior a way should be found to either associate Quantity objects as float/array or let the methods require Quantity objects in the first place.

Example of the code:

c3/c3/system/chip.py

Lines 57 to 89 in ef95330

	class Qubit(PhysicalComponent):
	"""
	Represents the element in a chip functioning as qubit.
	Parameters
	----------
	freq: np.float64
	frequency of the qubit
	anhar: np.float64
	anharmonicity of the qubit. defined as w01 - w12
	t1: np.float64
	t1, the time decay of the qubit due to dissipation
	t2star: np.float64
	t2star, the time decay of the qubit due to pure dephasing
	temp: np.float64
	temperature of the qubit, used to determine the Boltzmann distribution
	of energy level populations
	"""
	def __init__(
	self,
	name,
	hilbert_dim,
	desc=None,
	comment=None,
	freq=None,
	anhar=None,
	t1=None,
	t2star=None,
	temp=None,
	params=None,
	):

Related: https://github.com/shaimach/c3po/issues/6 and https://github.com/shaimach/c3po/issues/58