astrimid - Another day, another bug. Using <net...

Another day, another bug. Using `<netlabel` with `<schematicbox`. I see the example https://docs.tscircuit.com/guides/tscircuit-essentials/splitting-a-component-across-schematic-sheets uses `<resistor connections` prop which use `U1` references instead of `U1A` or `U1B`. This is fine, I guess. But it's unclear what behaviour should be if we try to attach the `<netlabel>` pulling some pins to the `GND` net for example. `<trace` is easier to understand for electrical connection and PCB trace. But as `<netlabel` is purely documentational (even though its `connection` and `net` properties implicitly creates a trace), placing it on schematic position using `schX` and `schY` has some strange behaviour wrt to attaching to pins or schematic boxes. So, using both `<netlabel` and `<schematicbox` with reference to `<chip` I think is undefined behaviour. Because if you reference chip name in netlabel connections, you would expect autocreated trace to be connected to chip pin. But as chip pin is being represented by a schematic box, you'd probably also expect the trace from schematicbox as well. But trace represents both electrical connection and pcb trace, and there's no schematic only wire that doesn't create a self referential connection. So as schematic box is introduced, I guess a schematic trace/wire is needed as well?