EntityQuery uses hard-coded langcode in revision-data joins, breaking translatable revisionable entities with custom langcode keys

Problem/Motivation

For translatable + revisionable content entities, core builds SQL joins that include a language condition when querying revision data.
In this path, the language column can be hard-coded as `langcode` for non-data-table joins, including the revision data table join.

This breaks entity types that define a custom langcode key (for example `language`) instead of the default `langcode`.
Result: SQL errors like “Unknown column ...field_revision.langcode in on clause” when opening translation/revision-related pages.

This is a correctness bug in SQL table alias/column resolution for entity query joins.

Steps to reproduce

1. Create a custom content entity type that is:
- translatable
- revisionable
- uses a custom langcode key (not named `langcode`)
2. Enable Content Translation for that entity type.
3. Create an entity and at least one revision.
4. Open the Translate page for that entity (or trigger a query that resolves latest translation-affected revision).
5. Observe SQL exception: unknown column `.langcode` in JOIN condition.

Proposed resolution

When selecting the language key for table joins, treat both data and revision data tables as entity-language-key tables.

Use the entity’s configured langcode key for:
- $entity_type->getDataTable()
- $entity_type->getRevisionDataTable()

Keep fallback behavior for other tables.

Example approach:

$data_tables = [$entity_type->getDataTable(), $entity_type->getRevisionDataTable()];
$langcode_key = in_array($table, $data_tables) ? $entity_type->getKey('langcode') : 'langcode';

This ensures joins target the actual language column defined by the entity type.

Remaining tasks

None.

User interface changes

None.

Introduced terminology

None.

API changes

No public API changes.
Internal query table/column resolution logic is corrected.

Data model changes

None.
No schema changes; only SQL generation logic is fixed.

Release notes snippet

Fixed an EntityQuery bug where revision-data table joins could hard-code `langcode`, causing SQL errors for translatable revisionable entities that use a custom langcode key. Translation/revision queries now correctly use the entity’s configured language key.