Combine multiple cardinality field loading into a single database query

Entity and field module kernel tests all pass, let's see how the rest looks.

Got some errors on CI I couldn't reproduce locally even with supposedly the same mysql and php combination, but pretty sure it's ordering.

Added a sort on delta ASC for each field table, still uses an index but it requires a temporary table and filesort - probably just on the rows that are returned, but not ideal.

mysql> EXPLAIN SELECT node_field_data.nid AS nid, node_field_data.langcode AS langcode, node__field_ingredients.field_ingredients_value AS field_ingredients_value, node__field_ingredients.delta AS field_ingredients_delta, node__field_recipe_category.field_recipe_category_target_id AS field_recipe_category_target_id, node__field_recipe_category.delta AS field_recipe_category_delta, node__field_tags.field_tags_target_id AS field_tags_target_id, node__field_tags.delta AS field_tags_delta, node__layout_builder__layout.layout_builder__l
field_ingredients node__field_ingredients ON node__field_ingredients.entity_id = node_field_data.nid AND node__field_ingredients.langcode = node_field_data.langcode AND node__field_ingredients.deleted = 0 LEFT OUTER JOIN node__field_recipe_category node__field_recipe_category ON node__field_recipe_category.entity_id = node_field_data.nid AND node__field_recipe_category.langcode = node_field_data.langcode AND node__field_recipe_category.deleted = 0 LEFT OUTER JOIN node__field_tags node__field_tags ON node__field_tags.entity_id =
node_field_data.nid AND node__field_tags.langcode = node_field_data.langcode AND node__field_tags.deleted = 0 LEFT OUTER JOIN node__layout_builder__layout node__layout_builder__l
ayout ON node__layout_builder__layout.entity_id = node_field_data.nid AND node__layout_builder__layout.langcode = node_field_data.langcode AND node__layout_builder__layout.delete
d = 0 WHERE (node_field_data.nid IN (1)) AND (node_field_data.langcode IN ("en", "es", "und", "zxx")) ORDER BY field_ingredients_delta ASC, field_recipe_category_delta ASC, field_tags_delta ASC, layout_builder__layout_delta ASC;
+----+-------------+------------------------------+------------+------+----------------------------------------------+--------------------------------------+---------+-------------+------+----------+-----------------------------------------------------------+
| id | select_type | table                        | partitions | type | possible_keys                                | key                                  | key_len | ref         | rows | filtered | Extra                                                     |
+----+-------------+------------------------------+------------+------+----------------------------------------------+--------------------------------------+---------+-------------+------+----------+-----------------------------------------------------------+
|  1 | SIMPLE      | node_field_data              | NULL       | ref  | PRIMARY,node__id__default_langcode__langcode | node__id__default_langcode__langcode | 4       | const       |    2 |    40.00 | Using where; Using index; Using temporary; Using filesort |
|  1 | SIMPLE      | node__field_ingredients      | NULL       | ref  | PRIMARY                                      | PRIMARY                              | 5       | const,const |   26 |   100.00 | Using where                                               |
|  1 | SIMPLE      | node__field_recipe_category  | NULL       | ref  | PRIMARY                                      | PRIMARY                              | 5       | const,const |    1 |   100.00 | Using where                                               |
|  1 | SIMPLE      | node__field_tags             | NULL       | ref  | PRIMARY                                      | PRIMARY                              | 5       | const,const |    2 |   100.00 | Using where                                               |
|  1 | SIMPLE      | node__layout_builder__layout | NULL       | ref  | PRIMARY                                      | PRIMARY                              | 5       | const,const |    1 |   100.00 | Using where                                               |
+----+-------------+------------------------------+------------+------+----------------------------------------------+--------------------------------------+---------+-------------+------+----------+-----------------------------------------------------------+
5 rows in set, 1 warning (0.00 sec)

However, that does fix all the test failures (except for the obvious performance test failures because those aren't updated yet) on CI.

We don't need to do #4 because we can ksort() the results. MR should be green now.

Since the logic here is very similar, it should actually be possible to combine the single and multiple cardinality queries into one as well. However once we do that, we end up with all columns for all fields in all rows of the result, which would slightly increase the risk of hitting max_allowed_packet as discussed in the previous issue. I think that all that's necessary for this is removing the split and using the multiple cardinality logic only, might give it a go in a separate MR.

edit: tried this, but there is indeed too much duplication in the results, let's stick with the original idea here.

MR is green and ready for review.

After this, we can do #3561960: Combine the database queries in ::loadFromSharedTables() and ::loadFromDedicatedTables() which should remove one more query-per-entity-load (e.g. probably 3-5 queries per page in core tests), which would mean all entities are loaded with a maximum of three queries - the initial load query, the single cardinality fields, and the multiple cardinality fields.

This can go on the same change record as https://www.drupal.org/node/3562172 - tagging to update that assuming this lands for 11.4.x

Nearly 10% reduction in queries on the 'front page cool cache' performance test justifies major I think.

Kicked off a fresh pipeline and tried to answer the question on the MR.

Updated the CR: https://www.drupal.org/node/3562172