#110441Per-record translation lookup slows down Page and Records module drastically
Description
Since v14.3.6 (#110281), `LocalizationRepository::getRecordTranslations()` matches translations with `(l10n_source = :uid OR (l10n_source = 0 AND l18n_parent = :uid))`. The second branch is unselective — `l10n_source = 0` applies to every untranslated record — so the lookup can no longer be resolved by a single index.
`DatabaseRecordList` and `GridColumnItem` call it once per rendered record for the delete confirmation hint, passing only the uid, so the method’s pid filter (`LocalizationRepository`) never applies and each call is unbounded across the whole table. On pages with many content elements the Page and Records modules take 20-60s longer than in v14.3.5 (approx 200000 enntries in tt_content). Both callers already hold the full record, which `getRecordTranslations()` accepts — passing it instead of the uid restores the pid restriction.