Potential non imported node delete solve

[samuelbray32]

Description

Within bridge restrict, was hitting error if table 2 not defined in the namespace. This change loads the free table from the connection and assigns it to the node, allowing for the restriction to be passed.

In testing this allowed me to remove the non part tables from the imports in SpyglassMixin._import_part_masters() and not hit errors in delete

I might be missing an issue this would cause in further restriction propagation or other use case, so feel free to reject if so

[CBroz1]

Thanks for your work @samuelbray32!

This PR could potentially contribute to spy #1002 by skipping nodes that we would otherwise need to add to _import_part_masters in the future. I'd like to roll it out as-is and then check in with user intuition about how unimported nodes should be treated

1. Ignored, as done here - potentially hitting the DJ error 1002 was designed to avoid
2. Raised as error, to explicitly cascade through all of spyglass

If the former, we can revisit this approach