BUG findClosestNode too slow if $node is already the matching one

[mhsdesign]

@nezaniel said that this query will take enormous amount of time - 5 seconds - on a raspery if $currentNode is already the site node:

$siteNode = $subgraph->findClosestNode($currentNode->nodeAggregateId, FindClosestNodeFilter::create(nodeTypes: NodeTypeNameFactory::NAME_SITE));

[mhsdesign]

We should investigate as we are about to add more usages of findClosestNode to the codebase ;)
Maybe you @kitsunet could please look into this? :D

Bernhard reconfirmed that

we should and it was rather awful

^^

[kitsunet]

Yep will do, sounds nasty!

[mhsdesign]

Also @dlubitz and me wondered why we dont use LIMIT=1 and rather map all rows to nodes and just return the first one.