fix: ReferenceNodes usage with mask set

[sruehl]

resolves #682
resolves #550

[sruehl]

Another way would be to add a factory function to node.go accepting a ExpandedNode. Might be a bit more efficient.

[kung-foo]

I think your idea for a static factory function sounds cleanest. It would make it clear what is happening, and who should be using it.

[sruehl]

ok, I rebased the branch on main (not sure if that was necessary) and added a commit migrating this to the factory function (method). Instead adding it as a static I added it to client analogous to the c.Node call. This could also be moved to node.go and made be private if the exposed NodeFromExpandedNodeID doesn't make sense outside the ReferencedNodes call

[kung-foo]

Can you add a few tests to cover the conversion?

[sruehl]

sure will do

[sruehl]

731d545 contains the most relevant test where the arguments ensure the flag is set and the conversion ensure those are unset

[kung-foo]

Tested with Prosys Sim 5.4.6 and Azure IoTEdge 1.4.371.60