New relationships and summary field

Tests and linting included.

Linting

Just looking at isolated query performance of the Root relationship i get 250ms in prod for 50 records. This being the query for the /admin/content view, plus the root relationship.

SELECT node_field_data.nid AS nid, users_field_data_node_field_data.uid AS users_field_data_node_field_data_uid, eh_for_node_field_data.nid AS eh_for_node_field_data_nid
FROM
node_field_data node_field_data
INNER JOIN users_field_data users_field_data_node_field_data ON node_field_data.uid = users_field_data_node_field_data.uid
LEFT JOIN (SELECT eh_child.id AS eh_child_id, eh_child.revision_id AS eh_child_revision_id, eh_parent.id AS nid
FROM
nested_set_field_parent_node eh_child
INNER JOIN nested_set_field_parent_node eh_parent ON (eh_child.left_pos BETWEEN eh_parent.left_pos AND eh_parent.right_pos) AND eh_parent.depth = 0) eh_for_node_field_data ON node_field_data.nid = eh_for_node_field_data.eh_child_id
WHERE (node_field_data.status = 1 OR (node_field_data.uid = 1 AND 1 <> 0 AND 1 = 1) OR 1 = 1 OR 1 = 1)
ORDER BY node_field_data.changed DESC
LIMIT 50 OFFSET 0

If i up this too much, or add a sort on say eh_for_node_field_data.nid, which I think will need to query the whole result first to then apply the sort and limit, then it starts to slow down. I'm not sure what this should scale too.

There's a cross join in the root relationship.

Correction, it's missing the vid/revision in the WHERE. That explains the slowness...

Fixes the join to include revision key if appropriate.

+ if ($revision_key = $entity_type->getKey('revision_id')) {

+ if ($revision_key = $entity_type->getKey('revision')) {

1000 rows on this site is more performant now.

SELECT node_field_data.nid AS nid, users_field_data_node_field_data.uid AS users_field_data_node_field_data_uid, eh_for_node_field_data.nid AS eh_for_node_field_data_nid
FROM
node_field_data node_field_data
INNER JOIN users_field_data users_field_data_node_field_data ON node_field_data.uid = users_field_data_node_field_data.uid
LEFT JOIN (SELECT eh_child.id AS eh_child_id, eh_child.revision_id AS eh_child_revision_id, eh_parent.id AS nid
FROM
nested_set_field_parent_node eh_child
INNER JOIN nested_set_field_parent_node eh_parent ON (eh_child.left_pos BETWEEN eh_parent.left_pos AND eh_parent.right_pos) AND eh_parent.depth = 0) eh_for_node_field_data ON node_field_data.nid = eh_for_node_field_data.eh_child_id AND eh_for_node_field_data.eh_child_revision_id = node_field_data.vid
WHERE (node_field_data.status = 1 OR (node_field_data.uid = 1 AND 1 <> 0 AND 1 = 1) OR 1 = 1 OR 1 = 1)
ORDER BY node_field_data.changed DESC
LIMIT 1000 OFFSET 2000

1. Needs a test for entitys with revisions
2. If you do a relationship to root, you can do a filter on root node ID, and you can display title/fields, but you can't do a filter on the title of the root node.