update diff logic to handle schema kind migration

[ajtmccarty]

IFC-990

updating a schema's kind puts the database into an unusual state that the diff was not capable of handling.
the green node has the updated kind and the red node has the old kind. they both have the same UUID and the red one has been deleted. this make sense logically, but the diff expected every UUID to link to one and only one node. it also expected that there would only ever be 2 nodes connected to a relationship, not 3

I made some changes to the diff cypher queries and the DiffQueryParser that reads those cypher queries to allow them to handle this unusual database situation correctly

[codspeed-hq]

CodSpeed Performance Report

Merging #5634 will not alter performance

_{Comparing ajtm-01302025-diff-support-kind-migration (b2ba0f9) with stable (c5e8e73)}

Summary

✅ 11 untouched benchmarks