Cannot add new translation if the latest affected translation revision of the source language is older than the default revision

The Needs Review Queue Bot → tested this issue. It either no longer applies to Drupal core, or fails the Drupal core commit checks. Therefore, this issue status is now "Needs work".

Apart from a re-roll or rebase, this issue may need more work to address feedback in the issue or MR comments. To progress an issue, incorporate this feedback as part of the process of updating the issue. This helps other contributors to know what is outstanding.

Consult the Drupal Contributor Guide → to find step-by-step guides for working with issues.

I just ran into the same issue working with translations and content moderation. Specifically when:

1. The user adds a translation (from EN to NL for example).
2. The user publishes both EN and NL.
3. The user then removes the NL translation.
4. More revisions are made for EN (these revisions no longer have a copy of the NL translation since it has been removed).
5. The the user visits the translation overview, somehow it seems the NL translation still exists, so the user can't create a new translation, and is also not able to delete the NL translation.

When I tried the latest patch I still found two issues:

• The translation overview uses the latest translation affected revision. Which made it seem like the NL translation could not be removed (since the NL langcode had an older translation affected revision). We should probably also check here if the latest translation affected revision is newer than the default.
• The entity repository EntityRepository::getActive() also loads the latest translation affected revision. This prevented creating a new translation from the default revision.

An updated patch is attached.

If the default revision still contains the translation, we can still allow older revisions to be loaded.

Appears to have some test failures