feat: Custom Structure chart parser

[Eatham532]

No description provided.

[cedar-debater]

just for reference, here is what it currently looks like

immediate feedback

1. do not allow a child node to have multiple parent nodes
2. no line crossing
3. you need some standard way to represent the group of "data flow & label", and a way for collision detection, and also fitting enough space.

i'd personally implement it by trying a very small scale, then haviing the code progressively scale up if it overlaps or has like 5 rows of data flows on top of the lines

im just not feeling very motivated to review the code rn sorry

[cedar-debater]

wait why specifically put emojis in

NOOO INCONSISTENCY MY ONLY WEAKNESS /j

(actual somewhat code review at #27 (comment) )

[cedar-debater]

WHAT DO YOU MEAN IT JUST PUTS COMMENTS IN THE SAME PR DISCUSSION???

nvm ig

[Eatham532]

Haha thanks for looking over this. Right now this pr was just experimental. Because i had no time to put effort in doing stuff myself (exams etc) i had an agent do stuff and it was experimental.

Also, im pretty sure a child can and should have multiple parent nodes. The example in the demo run is a good example