Remove the parameter queue and use the write_pending flag instead

[Guzz-T]

With these changes, the data to be written is stored directly in the field object, so that the values can also be set directly in the field via value.

This is indirectly a breaking change, as the value of the field changes when set() is called. This was not the case before. @Bouni, was there a specific reason why it was implemented this way?

Previously:

parameters.get(2)        >> 1°C
parameters.set(2, 2) 
parameters.get(2)        >> 1°C

Now:

p2 = parameters.get(2)   >> 1°C
parameters.set(2, 2)
parameters.get(2)        >> 2°C
p2.value = 3
p2                       >> 3°C                        

Relates to #221

[github-actions]

Coverage Report

File	Stmts	Miss	Cover	Missing
luxtronik
__main__.py	25	25	0%	3–66
collections.py	125	1	99%	304
datatypes.py	412	2	99%	61, 133
discover.py	58	1	98%	63
luxtronik/cfi
interface.py	168	13	92%	80–93, 243–244, 249
luxtronik/definitions
__init__.py	237	1	99%	172
luxtronik/scripts
__init__.py	35	5	86%	7–16, 51
discover_shi.py	60	60	0%	8–98
dump_cfi.py	14	6	57%	18–25, 29
dump_shi.py	15	6	60%	21–28, 32
performance_shi.py	63	63	0%	7–89
update_screen.py	105	82	22%	6, 20–41, 46–48, 51–61, 64, 70–75, 78, 81–85, 88–92, 95–97, 100–103, 106–111, 115–116, 119–126, 129–136
watch_cfi.py	32	16	50%	36–47, 50–56, 60
watch_shi.py	33	16	52%	38–49, 52–58, 62
luxtronik/shi
contiguous.py	121	2	98%	224–225
TOTAL	2439	299	88%

Tests	Skipped	Failures	Errors	Time
381	0 💤	0 ❌	0 🔥	35.728s ⏱️