Dm multi sync thread spawn and reference edges

[mkreider]

• DM can now create and read back edges describing pouinters/references between node fields (no linking to global addresses outside regular graphnodes yet). FW can interprete and execute this for all node types, but carpeDM limits it to timing messages and blocks fow now, this can easily be changed if so desired.
• multiple threads can be started vie startThread nodes. The Idx of a thread to be started has been converted to bitmask of all threads to be started, all freshly started threads are initialized with the current timesum of the calling thread and thus syncs all spawns to spawner. Output of thread attribute changed in dot to hex format to make bitmask clearer
• FW version bump to 9.0.0
• included manual test dots for new features

TODO: test referencing code - writeback of changes to immediate values (e.g. the rd and wr indices of a block to its command queue) if the node uses references. This works differently to nodes not using references and should be thoroughly tested

[skorsky]

Functional review:

1. Old pytests work after change of thread attribute for startthread nodes in dot files. For startthread thread=1 changes to thread="0x2", thread=2 changes to thread="0x4" and so on. The value is a bitmask. Attention: no change for origin nodes. Origins must assign exactly one thread.

2. dynpar{0,1} edges are missing after download of schedule.

3. The validation of schedules needs a check for valid thread numbers in startthread and origin nodes.

4. The simultaneous start of threads does not work as expected for 32 threads.

This pull request needs fixes before merge.