Bug: incorrect query generated by GetNodeRegistryAtHeight()

[capt4ce]

Description

I found a problem in the GetNodeRegistryAtHeight() query. If a there are 2 records under a group by, the query will consider any of the records, not only the latest one.

Steps to reproduce

1. create an artificial records in the node_registry table that have same id but different height.
2. make that first record to have registration_status=0 and the second one registration_status=2
3. run the original query. It will return that artificial node although the latest registration_status==2

Expected behavior

If such situation happens, the query should consider the latest state of the record.