Fixes: #11079 - Handle cables across multiple rear-port positions

[DanSheps]

Fixes: #11079 - Add supported path through modules and multiple rear-ports with different positions on same device

• Add support for pathing through modules.
• Adds some logic to generate split paths when path lengths vary

[DanSheps]

Not sure how I feel about the logging, could definitely remove it or modify it if someone has strong opinions.

[DanSheps]

Don't create the path. It would fail normally anyways, this just allows the cable to be created but not create the cable path.

[jeremystretch]

This is not a sufficient means of addressing the underlying issue. The assertions function as sanity checks: If they are being violated, we need to determine why and resolve accordingly. This might entail removing the assertions, or implementing other logic to accommodate the unexpected case. But merely logging them and avoiding creating the cable path is not a solution.

[DanSheps]

I am moving to a bit of a rewrite to properly account for at least this type of cable path. It should be ready for re-review in a few days.

[DanSheps]

I think this is ready @jeremystretch

[DanSheps]

I have some fine-tuning to do on a new SVG rendering and then I will push that code as well.

[DanSheps]

Things to note:

1. If there are 3 or more cables in the render, it will push the other stuff to the tooltip and only show the Cable ID/Name.
2. I have made it so it only puts unique cables in the node list per node. It does this in order to preserve termination and cable ordering (otherwise you might have cables ordered incorrectly which results in weird lines

[jeremystretch]

This has been a huge undertaking. Thanks for seeing it through @DanSheps!