Non-translatable multi-value fields load empty (loadMultipleCardinalityFields missing default_langcode guard)

Problem/Motivation

In SqlContentEntityStorage, loadSingleCardinalityFields() and loadMultipleCardinalityFields() both choose whether a row's value is keyed under the default langcode or the row's own langcode. The single-cardinality method guards that choice with empty on the default_langcode key; the multiple-cardinality method does not. Because of that, a default-translation row whose base-table langcode differs from the computed default langcode gets keyed under a non-default langcode and is then skipped for non-translatable fields, so a non-translatable multi-value field (for example a Paragraphs field) loads zero items even though its rows exist and are not deleted. This still happens in 11.4.4.

To reproduce: on an entity type with the language module enabled and a non-translatable multiple-cardinality field, load an entity whose default-translation row langcode does not equal the computed default langcode; the field count is zero and it renders empty.

The fix is to add the same default_langcode check to the if condition in loadMultipleCardinalityFields() that loadSingleCardinalityFields() already uses. No query change is needed because the default_langcode column is already selected. Confirmed on 11.4.4: the field returns to its real item count and renders again.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet